Ouch, that's a pretty serious restriction. Any plans to fix this any time soon?jclausius wrote:Has the label been modified through promotion? A modified label does not represent any known version of a folder found in any historical tree, and cannot be branched.
Pinning/sharing behaviour
Moderator: SourceGear
Yes. As previously mentioned, branching only works on "known" versions of folders. So when a label is modified, it no longer represents any known version of a folder. It is really an entirely new folder.Christian wrote:Blast, you're right, I've used label promotion to tweak the composition of the label. Now that's a real dissapointment. Can you see what I was trying to do?...
Label once sufficently happy that the latest version can be released;
Maybe tweak the composition of this label for a few last minute bugs;
Release (knowing that we can go back to the label at any time);
Carry on working on new features on the mainline;
Spin off a branch from the label when the need arises to create a hot fix.
However, I can see where it would be useful to create a new "branch" on this modified label. I'll log a customer feature request to create a new folder structure (recursively), and branch each file of the label into the folder structure.
Did you catch my follow up post. There was a problem discovered in one of the later Vault 2.0.x releases from branching anything from history. The problem will be fixed in Vault 2.1.Christian wrote:Any thoughts on what's going wrong.
Jeff Clausius
SourceGear
SourceGear
That's brilliant Jeff. I think this would be a real useful feature to have.jclausius wrote:However, I can see where it would be useful to create a new "branch" on this modified label. I'll log a customer feature request to create a new folder structure (recursively), and branch each file of the label into the folder structure.