...
SVN Best Practices:
Frequent checkins: At the end of the day, the code needs to be in a compliable stage and be checked in. It is much easier to review and integrate code if it is checked in in small chunks. A new feature or a bug fix will often take days or maybe weeks to complete.
However, it is important to check in your code frequently so the code is continuous integrated and everybody sees the latest changes. , but you should typically be checking in at least one piece of the feature per day if there are a lot of code changes.
Fine grained commits: Don't commit unrelated changes together with a fix.
Be responsible: Always check what you're committing: make sure you're only committing what you need. Do a svn diff of the files you're going to commit and check the changes.
Never break the build: Do not commit code that would break the compile. Trying Try to build your sources and making make sure that you add all the new files before you do a commit.
Document your commit: Always add a message with a meaningful explanation about the commit. If you are fixing a bug, remember to put a link to the bug in Jira.
...