Repository Organzation

[Ron Kunce]

I am looking for best approaches to organize and use our (new) Vault Repository. Specifically, I am concerned about working with Solutions in Visual Studio 2005 and maintaining the projects in Vault, where at some point a Soluton is moved from development to production yet continues to modified as new features are added. I have tried creating a new solution from the old with a different name to allow for addition of new features under the new name while maintaining the "baselined" prior version(s) for the ability to check-out modules and make quick maitenance changes without having to roll-back the current version with new in-work features. However, this solution leads to proliferation of duplicate code in the repository under differnt names and since we haven't yet established a Solution naming Convention to track which version is which it gets difficult to know which is the current in-work version and which is the maitenance version without looking at indviduals modules to find which has the latest changes -- and even that is not foolproof way to tell them apart. Using the comparisson also helps but takes longer to use and if one is unfamiliar with the code or haven't visited it for a long time, it is still difficult to tell which Solution is which.

Does anyone have any ideas on how to keep it organized or can point me articles on this subject?

Ron K.

[lbauer]

You may want to use branching and merging for your development process. Here are a couple of useful links to describe branching and a possible trunk and branch structure for ongoing development.

http://www.ericsink.com/scm/scm_branches.html

http://support.sourcegear.com/viewtopic.php?t=193

Let me know if you have additional questions.