Development guidelines

(Difference between revisions)

Revision as of 22:08, 15 March 2007

If you only intend to make a few commits you should post your code on the forums and ask for someone to commit it for you.
If you intend to be an active contributor contact baker99@gmail.com with reasons why you need access, your coding experience, and preferably the first piece code you want to commit.
Every commit must have a corresponding jira issue, this issue code must be the first item in your commit message, for example a typical commit message looks like this WW-778 - Improve Rendering Peformance.
Check your commit does not break SVN, i.e. World Wind still builds, if you repeatedly break SVN your commit privalages will be revoked.

If you see an unassigned issue you wish to take on you can freely assign it to yourself.
If you see an assigned issue you wish to take on or help with contact the current assignee or email baker99@gmail.com, never assume an issue has been abandoned.
Issues with more votes should be priortised, if you have several issues assigned to you fix the ones with most votes first, or unassign those issues and let someone else fix them.
If you believe you have fixed an issue, select resolved, and ask for someone else to verify your fix, they should then select fixed or comment on your issue if there are still problems.