SC Newbie Question

dmoring · Post by **dmoring** » Wed Oct 24, 2007 4:34 pm

As the quantity of projects/versions have grown, I have recently begun using source control (and Vault makes it VERY easy).

I have a silly, but important question. I need to increment an application/codebase (VS 2005 IDE) for a new version - i.e., to "copy" the code base from the original version and begin work on the copy while making sure that changes applied to the new version are not applied to the old codebase (whose featureset is now frozen and will only be opened/modified for new versions) and changes (i.e., bugfixes) to the old version are not copied into the new version.

The best way seems to be a "Branch" in the same repository. Is this correct? Are there any commands to avoid or pitfalls to this to ensure complete codebase separation? Thanks in advance for any guidance!

lbauer · Post by **lbauer** » Wed Oct 24, 2007 6:23 pm

A branch would work for this. Any changes in the branch would be independent of the original project that you branched from. Some examples here:

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

Or you can label the project at version "X" and continue work there. You can always Get the label, which would get the project in the state it was in when you labeled it.

Another option, if you don't need the file history, is to do a Get of your project and then add those files to a new folder in the tree. You'd need to unbind the project first before adding it to the new location in the folder tree.

dmoring · Post by **dmoring** » Thu Oct 25, 2007 2:05 pm

lbauer wrote:A branch would work for this. Any changes in the branch would be independent of the original project that you branched from. Some examples here:

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

Big thanks. Exactly what I needed to know. I'm also going to work with labels a bit - the goal being to minimize the number of non-Major-Point branches I'm making.