Well, when I hired my current company a year ago, I was tasked with moving our development teams from VSS. They already had in their head that they wanted Subversion, and since I had experience using and setting up subversion, I was a good candidate. At first I tried to sell TFS because it solved the problem I am in now, but since the money is tight and Subversion is free ... well, you get the idea. In any case, I modified the propsal, and the only thing that stands in the way is the following.
I proposed to save only our source code in SVN, and all documentation, release builds and other artifracts projects will be stored on our SharePoint portal, so we do not need to provide third-party developers with access to SVN. When I presented this proposal, everything was excluded, but the question arose about how to manage synchronization between artifacts (example: "How is document x version 3.1.2" associated with release 4.5.2). My initial reaction was to create a section on the SharePoint portrait page for each new version, which will store artifacts (and track changes, too). Is there a better way to do this? Does anyone know who does this? Or any integration packages for synchronizing SVN with SharePoint?
Here is some information about the development environment of companies. All our software is intended for internal use, we do not sell anything, so our customers are all on their own. We have 2 types of developers: 1. those who care about the support and configuration of third-party software, and 2. those who write proprieatry software (where I fall). Our software that we write is mostly .NET, but third-party software is found all over the board (COBAL, C, FORTRAN, Other crap, which no one else cares about).
Please consult, as I need to get this soon. I hate vss !!!!!!!!!! and i need help!