THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
http://www.asterisk.org/developers/svn-branching-merging
http://www.reactos.org/wiki/index.php/Best_practices_for_working_with_branches
http://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING
http://svn.collab.net/viewcvs/svn/trunk/contrib/client-side/
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html
NOTES:
- a filter can be created to send all unresolved issues to the dev list
- JIRA is used as a tracker not a place for discussion
- TODO do we want a separate project for design/best practices discussions
- possibility of setting up a custom workflow
- demonstrate design/practices as opposed to scheduled work
- tagging issues with multiple components so that an issue is marked with its real category but can also be marked with a meta category like "design" or "best practices" which would allow us to group them in a view and be able to report on them
- need to sync all the bits and pieces in jira and confluence so we have a cohesive view of the work that needs to be done and planned for
- all snapshots should be resolved before the final testing is done on what will ship