...
Prior to submitting a patch or checking in code, you are required confirm step 6 as above mentioned. It takes approximately 30 minutes to 1 hour to run entire build (depending on the hardware you are running on). Only then should you check-in (commit) your code or submit your patch. If you're checking in code to the repository, you can confirm that your check-in didn't break the build by looking at our continuous integration server.
...
- Commit locally, following the Commit Log Guide.
- Use git format-patch
- Make sure your patch applies cleanly.
- More tips from git's SubmittingPatches
How to submit a patch
- Create an issue in the issue tracker if one does not already exist.
- Update the issue:
- Attach the patch file to the issue
- Add the label, "Patch", once it has been attached. Assign the issue to mifosdeveloperqueue. This adds the patch to the patch queue. The "patch" label is removed if a patch is not ready for review or was rejected.
- Watch the issue (click the envelope icon to the right of "Watchers")
- Provide a link to relevant mailing list discussion(s) within the issue comments
- When the patch has been accepted, the issue will be resolved and assigned back to you (the contributor).
...
Break the build
If you break the build, do it in style!
How to accept a patch
- apply patch build, test, and push the code to sf.net
- resolve the issue "Fixed"
- reassign the issue to the patch submitter
- reply to the
[PATCH]post on the mifos-developer mailing list
...