title: Structure of Projects in Version Control
body: <p>I know there are at least 10 different ways to structure project in version control. I'm curious what some methods being used are and which ones work for you.  I've worked with SVN, TFS, and currently/unfortunately VSS.  I've seen version control implemented very poorly and just OK, but never great.</p>
  
  <p>Just to get the ball rolling, here is a review of things I've seen.</p>
  
  <p>This example is SVN-based, but applies to most VCS's (not so much to distributed version control).</p>
  
  <ol>
  <li><p>branch the individual projects that are part of site
  /division/web/projectName/vb/src/[trunk|branches|tags]</p></li>
  <li><p>branch the whole site, in the case I've seen, the whole site except for core components was branched.
  /division/[trunk|branches|tags]/web/projectName/vb/src/</p></li>
  <li><p>Use main-line a default, only branch when necessary for <strong>huge</strong> changes.</p></li>
  </ol>