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 would have 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 proposal and the only thing standing in the way is the following.
I proposed that we store only our source code in SVN, and all documentation, release builds, and other project artifacts 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 accepted but the question arose about how to manage the synchronization 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 project page for each new release that will hold the artifacts (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?
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 maintenance and customization of third party software, and 2. those who write proprietary 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 languages that no ones cares about any more).
What we do internally is putting all docs under our version control system, I think it’s much easier. Then, of course, you have to give access to not-developers.
In your case, using SVN, why don’t you put everything inside and then use the webinterface to give access to the stakeholders? It’s easy enough for them 😛