title: SVN project structure
body: <p>We are moving to SVN from VSS and are debating the project structure. 
  We are debating two proposals displayed below. </p>
  
  <p>No. 1 seems simpler for development support since a Project release version is tied to a
  tag and the developer would only need to perform an update on that tag to immediately get to work.</p>
  
  <p>No. 2 insures that all Projects and Dependencies can be developed independently but 
  building a particular release version means knowing the tags of the Project and all
  it's Dependencies.</p>
  
  <p>Are there obvious comparative benefits between the two? 
  Any gotchas in the two structures? or are there better structures out there?</p>
  
  <pre>
  1.
  Development  
    + trunk  
      Project1  
      Project2  
      Dependency1  
      Dependency2  
      Dependency3  
    + branches  
    + tags  
  
  2.
  Project1  
    + trunk  
    + branches  
    + tags  
  Project2  
    + trunk  
    + branches  
    + tags  
  Dependency1  
    + trunk  
    + branches  
    + tags  
  Dependency2  
    + trunk  
    + branches  
    + tags  
  Dependency3  
    + trunk  
    + branches  
    + tags  
  </pre>