Source Repository Use
We're using common best practice.
- Trunk - should always build and pass tests.
- Branches - used for larger changes that could break Trunk such as at release time or for large features
- Tags - snapshots usually for releases
- write telling log messages because several people will read your diffs. State version numbers for merges
- if you add .txt or .py files to the repository then please make sure you have svn:eol-style set to native which allows checkin/checkout in native line-ending format.
