How to submit a patch
Any help is very much appreciated.
In order to start
- Create a Jira issue for any specific improvement that you'd like to contribute
- Wait until a committer Accept the issue (it will become Opened). This will give you the assurance that your patch will be incorporated in the next release.
- Assign yourself to that issue.
- Start progress when you start working on it.
- After you completed your implementation, Attach a patch file to the issue. (output of the command svn diff).
- Move that issue to a Resolved state (a committer will get in touch with you at that point)
How to make a change
Read Developer setup for more information on how to get set up (Subversion, JIRA, IDEs...) and Development guide to get your bearings and do your first build. All development related pages are under Development topics.
 | If you ran into problem have questions around coding/design please send an email to the dev list. More info on our mailing list can be found here. |
In order to get your work committed more quickly, it's helpful to
- follow the development standards
- provide tests for the added features. Both unit tests and acceptance tests are needed.
- patch the documentation as well!!!
Please give any feedback you might have in the Contributors feedback page. You might want to watch this space as well in order to get update notifications (go to the wiki tips for instructions on how to do this).
How to become a committer
To become a committer of xplanner, you need to demonstrate:
- Good design skills
- Good testing skills (AT and UT are coded before the implementation starts)
- Knowledge of the infrastructure and the project design
- Commitment to the project (you submitted several patches)
This usually means that you would start by contributing several patches that would get reviewed by other commiters and incorporated. After the committers get a good feel of the quality of your solutions, you would be granted commit access.
