title: Configuration Management with Subversion and SharePoint help
body: <p>Ok, when hired on to my current company a year ago, I was tasked with migrating our development teams from VSS.  They already had it in their minds that they wanted Subversion, and since I had experience using and setting up subversion, I was a good candidate.  I first tried to sell TFS because it woul dhave solved the problem I am in right now, but since money is tight, and Subversion is free... well you get it.  Anyway, I have finalized the propsal and the only thing standing in the way is the following.</p>
  
  <p>I proposed that we store only our source code in SVN, and all documentation, release builds, and other project artifracts be stored in our SharePoint portal, so we don't have to give non developer stakeholders access to SVN.  When I presented the proposal, all was excepted but the question arose about how to manage the syncronization between the artifacts (Ex: How to is document x version 3.1.2 associated with release 4.5.2).  My initial reaction is to create a section in the SharePoint porject page for each new release that will hold the artificats (and keep track of changes too).  Is there a better way of doing this?  Does anyone know of anyone doing this?  Or any integration packages to sync SVN with SharePoint?</p>
  
  <p>Here is some info on the companies development environment.  All of our software is for internal use, we sell none of it, so our customers are all in-house.  We have 2 types of developers: 1. those who take care of maintainance and customization of third party software, and 2. those who write proprieatry software (which is where I fall).  Our software we write is mostly .NET, but the 3rd party software is all over the board (COBAL, C, FORTRAN, Other crap that no ones cares about anymore).  </p>
  
  <p>Please advise, as I need to get this submitted soon.  I HATE VSS!!!!!!!!!!  and I need relief!</p>