Managing parallel code in VSS

Hi,

I have a project in VSS that keeps changing with each release version I have.

The way I manage this currently is through the use of version labels.

I have major and minor version for releases.

So I create a new project Version1 for say version 1.0.0 and keep checking in code for all subsequent releases in this project with labels.

Now, when I need to move to the next major version, say 2.0.0 I copy all the source to a new project called Version2 and start working with it as before.

The problem with this structure right now is that if the current version to be released next is say 1.0.2 but I also have code changes for the next version 1.0.3, I end up keeping all this code on the local system.

I would appreciate if someone could suggest a better way for managing this scenario.

I want the code changes made in 1.0.2 to be available in 1.0.3 as well.

Thanx

[982 byte] By [Praachee] at [2008-1-7]