Examples of some SVN best practices and policies:
- Don’t use versioning like it were a backup tool.
- Commit as soon as your changes makes a logical unit.
- Be precise and exhaustive in your commit comments.
- Never ever break the trunk.
- Use a sane repository layout
- Commit logical changesets
- Use the issue-tracker wisely
- Track merges manually
- Understand mixed-revision working copies
- Be patient with large files
- Work around commands that don’t understand copies/renames
- Know when to create branches
- Think Twice before Committing
- Never commit code that doesn’t compile
- Test your changes before committing
- Double check what you commit
- Always add descriptive log messages
- Respect other developer’s code
- Announce changes in advance
- Code review by other developers
- Take responsibility for your commits
- Don’t commit code you don’t understand
- Don’t commit if other developers disagree
- Backport bugfixes
- Use bug tracking system numbers
- Tags and branches
- Don’t add generated files to the repository
- Commit complete changesets
- Don’t mix formatting changes with code changes