-
Notifications
You must be signed in to change notification settings - Fork 21
Developer Notes
Bernhard Froehler edited this page Nov 13, 2017
·
5 revisions
If you would like to contribute to bfstop, you're more than welcome to do so!
- You can check if there is an open issue that interests you in the Issue tracker
- If you have got a cool new feature in mind, head over to the Issue tracker as well and add it. Or if you feel like immediately diving into the implementation, fork bfstop, implement your enhancement and provide a pull request!
- Testers are always welcome, especially for newer versions and betas/release candidates. Grab such a version (as described under Specific Versions), go over to the Test Cases section and run through some of the scenarios described there in a test server environment!
The following changes are required when a new release is done (i.e. when the version number needs to be changed):
- In bfstop, com_brstop and pkg_bfstop: adapt version number in deploy.sh and bfstop.xml
- In bfstop and com_bfstop, adapt download link and version number in update.xml (moved to a separate server now, not in the repository anymore)
- In wiki on download page, create new download link, move old download link to "specific versions" page.
- update extensions page (extensions.joomla.org)
- Add language files in respective folders (typically copying the english version is a good start):
- bfstop/language
- com_bfstop/admlang
- com_bfstop/site/language
- Add references to language files in the bfstop.xml files