-
Notifications
You must be signed in to change notification settings - Fork 19
Developer Notes
codeling edited this page Aug 13, 2013
·
5 revisions
If you would like to contribute to bfstop, you're more than welcome to do so!
- You can either check if there is an open issue you could look into the Issue tracker
- If you have got a cool new feature in mind, the suggestion would be to go over to the Issue tracker as well and add it. You could also 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](wiki/Specific Versions)), go over to the [Test Cases](wiki/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
- In wiki on download page, create new download link, move old download link to "specific versions" page.
- update extensions page (extensions.joomla.org)
[Language Changes](wiki/Language Changes)
- Add language files in respective folders:
- bfstop/language
- com_bfstop/admlang
- com_bfstop/site/language
- Add references to language files in the bfstop.xml files