...
- be stoked, don't panic!
- as soon as you notice you've broken the build, please try to fix the build immediately
- if you can't fix it within a couple of hours, revert head/master to the last stable revision
- if you aren't able to fix it, can't/didn't revert, and need to log off at the end of the day, let other developers know on IRC and send an email to the mifos-developer mailing list detailing
- why the build (might) be broken
- what (might) need to happen to fix it
- never check in code onto a broken build (unless you are working to fix the broken build)
- if you notice that someone else may have broken the build
- reach out to them, ask them what's up on IRC and the mailing list
- offer to help fix the build, and let folks know you're doing so on IRC and/or the developer mailing listnever check in code onto a broken build (unless you are working to fix the broken build)
- work against a known good revision
- don't "commit and split", try to integrate your work early in the day
- merge your code into a branch starting with the name "hudsonBuild", like "hudsonBuildTryNewDatabaseSettings", and push the branch to sf.net. Hudson will automatically build any branch in head named thusly. When done, delete the branch.
...