title: My very small company has reached the point of needing a VCS. I'm trying to plan our actual version control strategy first
body: <p>First and foremost, please excuse my writing: I'm a programmer fresh out of college with minimal professional experience. If anything is unclear, please bring it up and I'll do my best to clarify.</p>
  
  <p>I'm looking forward to using a VCS to help us to organize everything. Keeping track of bug fixes, development of new features, merging, and development of new editions should simplified, clarified, and made much easier.</p>
  
  <p>This is how we plan to use version control (given my fledgling understanding of VCSs):</p>
  
  <p>For the sake of a clear example, we'll call our current and released version of the software V1 and in-development next version V2.</p>
  
  <ul>
  <li><p>We plan to start with V1 as the trunk of our tree.</p></li>
  <li><p>A branch will be made for development of V2. This branch will never be merged back in, thus it is effectively the new trunk for V2.</p></li>
  <li><p>Branches would be split off of this new trunk for development of new features for V2 and merged back in when they are complete.</p></li>
  <li><p>Should bug fixes be needed for V1, branches would be made off of the V1 trunk, completed, and merged back into the V1 trunk. V2 development would need to pause as the V2 trunk updates from changed V1 trunk, then all V2 branches update from the newly changed V2 trunk. Then various V2 branches could resume development. </p></li>
  <li><p>When enough features have been branched off of the V2 trunk, completed, and merged back in, eventually it will be time to release V2 and start on V3. V3 will branch off of V2 and never merge back in (like V2 did from V1), and the process begins again.</p></li>
  </ul>
  
  <p>Is this a reasonable model? Will it be effective? Is it likely to develop issues over time due to my uneducated attempt at planning?</p>
  
  <p>Please let me know anything else I can provide to help you to help me. Thank you!</p>