Maintaining versions in VSS for various releases and products
Posted on 2004-08-02
We have a product for which there are multiple major releases (e.g. 1.0, 2.0 etc.) and minor releases(e.g. 1.0.1, 1.0.2 etc.).
We would like to store the source code in such a way that we should be able to extract the whole source code for any (major or minor) release at anytime.
For a major release, there could be 30 to 40 minor releases. We have few other products that share the files of this product. We would like to maintain the source code of other products in VSS as well.
Source Code consists of thousands of C++ files lied in multiple sub-folders. can anybody suggest how we should maintain the VSS structure?
(I have browsed through the Help for the "Label", "link", "branch" options in VSS).
Expecting the solution from you expert guys for 500 points.