Code

Collection of SubVersion (SVN) Best Practices

Examples of some SVN best practices and policies:

  1. Don’t use ver­sion­ing like it were a backup tool.
  2. Com­mit as soon as your changes makes a log­i­cal unit.
  3. Be pre­cise and exhaus­tive in your com­mit com­ments.
  4. Never ever break the trunk.
  1. Use a sane repository layout
  2. Commit logical changesets
  3. Use the issue-tracker wisely
  4. Track merges manually
  5. Understand mixed-revision working copies
  6. Be patient with large files
  7. Work around commands that don’t understand copies/renames
  8. Know when to create branches
  1. Think Twice before Committing
  2. Never commit code that doesn’t compile
  3. Test your changes before committing
  4. Double check what you commit
  5. Always add descriptive log messages
  6. Respect other developer’s code
  7. Announce changes in advance
  8. Code review by other developers
  9. Take responsibility for your commits
  10. Don’t commit code you don’t understand
  11. Don’t commit if other developers disagree
  12. Backport bugfixes
  13. Use bug tracking system numbers
  14. Tags and branches
  15. Don’t add generated files to the repository
  16. Commit complete changesets
  17. Don’t mix formatting changes with code changes

Leave a thought

%d bloggers like this: