SVN Best practices

• Update your svn projects before start working 
• Do not commit broken/error/unstructured code/functionality  (Test before committing if possible!)
• Commit as soon as a piece of the functionality is completed
• Branch life should not be too long living branches increase merge conflicts , This forces you to keep small units of work
• Every commit should have a purpose and meaningful comments. Commits with no purpose to be avoided, If possible,one functionality whole set of files should be commits at once 
• Here are the bad comments: "update" , "modification of new features"
• Here are the good comments: "Adding new classes to cater to requirement spec 1.1"