SVN user guidelines
- by Oliver Moran
I have been tasked with writing a set of user guidelines for SVN for developers in my company.
The guidelines are to be solely from a user perspective (e.g. commit comments, when to commit) and not from an administrative perspective (e.g. when to tag, how to structure). An administrative guideline will be written in a separate document.
We are an app development house involved also in embedded development. So our developers range from HTML5 and Flash to Java and C. Some of our coding involves forking very large (millions of files) code bases. Other parts involve us engaging in ground-up development.
Are there any best practices for use of SVN from a user (i.e. grunt developer) perspective?