I need help planning and setup SubVersion (from [url removed, login to view]) for use in our daily web development. I'm new into this and we've not been using source control before. I look for contact to an experienced person, that has huge experience in planning, setting up and using source control for Microsoft projects using Subversion.
Right now we need the basics setup, but we would like to continue improving afterwards, with automated builds and testing.
My needs at this moment are:
1. Planning structure for repository. We have multiple projects using multiple technologies. Our web projects are using IIS/ASP, DLLs and database using Visual Studio 6. Other projects are VC++ using Visual Studio 2003 and others are database using MS SQL Server 2000. How to arrange all this in Subversion?
2. I would like to limit access for each developer only to view and edit parts of our website project. I would like to hire freelance people, to work only at a certain feature of the site. Can I do this and how do they test? The asp pages will not execute on their local machine, as database and server dlls is needed to get the site working. So the developer should be able to checkin or store working copy directly on his own area on dev server. I dont know how this scenario is handled the best?
3. How is dev,stage,q&a,prod handled and what setup makes sense for us?
Only serious and experienced persons that has dealt with my exact setup, should apply. I look forward hearing from all of you great experts :-)