I just upgraded from 3.1.2 to 4.1. After the upgrade I branched one of my projects. I went in to the branch through the Vault Client to view labels and the branch does not contain the labels that are in the project that I branched from. I have not done any branching before so I'm not sure if there is an issue with my upgrade or if Vault does not attempt to carry over the labels. Can you please provide some insight as to whether or not Vault supports carrying over labels during the branch process.
Thanks.
Is Branching Supposed to Keep Labels?
Moderator: SourceGear
The labels aren't branched over. If they were, then when you performed a Get by Label, you'd might get duplicates of the files. The labels that were there belong to the original.
I you want, I can take a feature request to branch the labels over too. I'm not sure it's a good idea though or feasible.
I you want, I can take a feature request to branch the labels over too. I'm not sure it's a good idea though or feasible.
Thanks for the quick reply. That makes some sense to me but here is my scenario that I was considering.
I have a Visual Studio 2003 project and want to convert it to Visual Studio 2005 (yes, I know it is 2008 and there is an entirely new version of Visual Studio out there
). I'm was trying to decide a good approach to take for the conversion.
Approach A: Label the source and branch the source (trunk) to a "Backup" branch which would be similar to a Release branch. Do the conversion against the trunk, fix, and checkin. In the future, if I need to work against the 2003 project, do a GET against the "backup" branch, make changes, check in, and deploy.
Approach B: Label the source and branch the source (trunk) to a "Conversion" branch. Do the conversion against the branch, fix, checkin. Merge the changes from the branch into the trunk, resolve conflicts, check in. In the future, if I need to work against the 2003 project, I could do a GET against the label in the trunk that I applied before I branched the conversion branch.
I understand that there are many factors that go into branch scenarios, but was looking for any insight you may have into this scenario at a broad level.
Thanks.
I have a Visual Studio 2003 project and want to convert it to Visual Studio 2005 (yes, I know it is 2008 and there is an entirely new version of Visual Studio out there
). I'm was trying to decide a good approach to take for the conversion.Approach A: Label the source and branch the source (trunk) to a "Backup" branch which would be similar to a Release branch. Do the conversion against the trunk, fix, and checkin. In the future, if I need to work against the 2003 project, do a GET against the "backup" branch, make changes, check in, and deploy.
Approach B: Label the source and branch the source (trunk) to a "Conversion" branch. Do the conversion against the branch, fix, checkin. Merge the changes from the branch into the trunk, resolve conflicts, check in. In the future, if I need to work against the 2003 project, I could do a GET against the label in the trunk that I applied before I branched the conversion branch.
I understand that there are many factors that go into branch scenarios, but was looking for any insight you may have into this scenario at a broad level.
Thanks.