Hi guys,

We have a POS system that we send out to different sites and continually send different versions of our software. Sometimes different sites have different versions, so we have to be able to manage different versions at the same time.

Right now we are using Visual Source Safe v. 8 and we use the label feature to keep track of different versions of the software.

Our main concern is to be able to keep track of different versions, we need to be able to go back to a previous version and add functionality or fix a bug in that previous version. I'm guessing that 99% of the time that added functionality/bug fix will also have to go in the current version being developed but maybe in exceptions it will be required only for that previous version only.

How can Visual SourceSafe facilitate this scenario? I know about the labeling to keep track of versions, but how about going back to a previous version and making changes that will/will not affect the current version. I've been reading some about the "branch" feature, seems like that might be a possibility. Any input or experiences in this type of scenario will be appreciated.

Thanks.