Sam Reid
Welcome! Just a few things to note about our development process,
which may or may not be described on the wiki somewhere:
- Try to commit work against some open issue. We're all guilty of
not following this sometimes, especially for e.g. checkstyle-related
fixes.
- When you create a new Issue, leave it as New and without an owner
for a little while to allow for comment before assigning it to
yourself, moving it to Accepted, assigning a Milestone, etc.
- Include the Issue # in your svn commit message, e.g.
$ svn commit -m "Issue 123 ; fixed blah blah..."
- Include the Revision # (either "revision 123" or "r123") as a
comment in the Issue when you commit a fix against an issue. This
allows a reviewer to quickly find the diff and start the code review
process if necessary. I usually just cut n' paste the svn commit
command that gives you the "Committed revision 123" note at the
bottom.
- Fixed issues should be moved to Verified by either the original
submitter or a developer other than the committer of the fix.
- Revolutionary changes should happen on a branch first.
- We don't vote on things very often, it's more proceed until veto.
I'm sure the other devs will chime in if I missed or mis-represented
anything. :)
michael