title: What guides or standards do you use for version control in your team?
body: <p>I'm starting to do a small amount of development within my company.  I'm intending to use Git for version control, and I'm interested to see what guidelines or standards people are using around version in their groups, similar to coding standards are often written within the group for the group.</p>
  
  <p>I'm assuming there will be things like;</p>
  
  <ul>
  <li>Commit often (at least every day/week/meeting etc)</li>
  <li>Release builds are always made from the master branch</li>
  <li>Prior to release, a new branch will be created for Testing and tagged as such.  only bug fixes from this point onwards.  The final release of this will be tagged as such and the bug fixes merged back into the trunk</li>
  <li>Each developer will have a public repo</li>
  <li>New features should get their own branch</li>
  </ul>
  
  <p>Obviously a lot of this will depend on what VCS you're using and how you've structured it.</p>
  
  <p>Similar Questions;<br>
  <a href="https://stackoverflow.com/questions/273695/git-branch-naming-best-practices">git branch naming best practices</a><br>
  <a href="https://stackoverflow.com/questions/2006265/is-there-an-standard-naming-convention-for-git-tags">Is there a standard naming convention for git tags?</a></p>