Standard practices for Subversion

Question

I\'m wondering if there\'s any other factors to consider for standard practice of using Subversion.

The few I have are:

• Directory structure of /tags /tr

Answer 1

Branches are a good idea for making big, possibly-breaking changes. If trunk is being updated at same time, occasionally merge trunk to branch to keep the branch updated.

Commit an atomic set of related changes. Don't do a big commit with unrelated changes all over. This makes tracking specific changes much easier.

You can have multiple checkouts of the same source - useful if experimenting with unrelated changes.

Avoid committing broken code, or code with failing tests, or with other outstanding issues.