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

You should always do an update before committing, to prevent possible conflicts with other commits made by other people and painful merges.

Also, every commit should contains something meaningful, like a bugfix, or a new feature, or some improvement to an existing one, something that can be meaningful described in the log message. A source control tool is not a backup tool, so "end-of-the-day" commit without a meaningful content should be avoided.