title: Best practices for source control and bug fixes
body: <p>If we need to issue a bug patch that does not include current development that has been  committed, or any changes from their current version, what should be done to make the process safer and with lower overhead?</p>
  
  <p>We are currently using Subversion for our source control in a small (3 developers) team primarily developing in Visual Studio 2008. We anticipate that the team may group to 8 developers over the next year, and for any previous release support to become more complicated. While most customers are on the current release, some are further behind.</p>