Vault - Branching does not copy labels

lawrep · Post by **lawrep** » Mon May 17, 2004 2:09 am

When I do a branch in Vault (v2.0.2) I noticed that although the entire history of a file gets copied, any labels do not. Is this to be expected? If so is there another way that I can create a copy of my source with its entire history?

Post by **jclausius** » Mon May 17, 2004 7:56 am

Thanks for the report. It seems when the switch was made to the new style of labels, the history code that deals with labels does not respect branching origins.

I've logged this problem, which should be fixed in an upcoming release of Vault.

lawrep · Post by **lawrep** » Mon May 17, 2004 8:14 am

Do you have any idea of when this might be? It is a bit of a major problem as we've just moved our VSS databases over to Vault but have now stopped checking in changes for our next release because of this issue.

Thanks.

Post by **jclausius** » Mon May 17, 2004 8:47 am

Since Vault 2.0.3 was released last week, we haven't set any dates for future Versions of Vault.

I don't have an understanding of your process, so this may be way off the mark, but would labelling the new branch help?

lawrep · Post by **lawrep** » Mon May 17, 2004 9:41 am

Just to give you an overview of our setup we currently support 3 versions of our product and hence require 4 source paths - 3 for maintenance purposes and 1 current development. When we are about to do a release we label the current development path i.e '6.5 code cut off' and then copy/branch the tree to create a new 6.6 path. The 6.5 path then keeps going for maintenance which contains a history identifying when it was releases, and a new path which also contains a history including details of releases.

Anyway, unfortunately it wouldn't really help to label the new path as the problem is that we will still lose all the older release labels. This is currently important for our root cause analysis where we use the file history to carry out diff's to see which version and release a bug was possibly introduced.

I suppose it is more of an issue because if we decide to go ahead then the old labels will be lost from the file history forever.

Thanks.

Post by **jclausius** » Mon May 17, 2004 10:07 am

I see. You want the labels including sources (from branch) to be able to diff within the History Explorer when a suspected bug arises.

There is a temporary work-around until the fix is implemented, and yes, it is a major, major kludge. You could get the label(s) of the "source" file, and then within the branch, diff against the different labels that were retrieved to disk.

lawrep wrote: I suppose it is more of an issue because if we decide to go ahead then the old labels will be lost from the file history forever.

I don't understand what you mean by this sentence. Can you elaborate more here?

lawrep · Post by **lawrep** » Tue May 18, 2004 8:48 am

I meant that once we do one branch, say to create a 6.6 release, this path will not contain the old labels. Subsequently any further releases taken from this path will also not contain the old labels - as even if you have fixed the problem there will be no labels to copy.

Anyhow, I think we have a solution for our current situation. Because we have only just moved over to Vault and there have been limited changes I can re-create the new release path by importing from the old VSS database and then simply renaming it. (the previous release was in VSS).
Hopefully then by the time we come to creating our next release branch (in approx 6 months) you will have a fixed this issue?

Thanks for your help

Post by **jclausius** » Tue May 18, 2004 9:45 am

I'm uncertain why you think the branched item will not contain any of the source labels. Any fix we provide for this problem will be retro-active.

In other words, in Vault 2.0.3, labels applied against the source of a branch do not display in History Explorer of the branch. When the fix is implemented, these labels will be displayed in History Explorer.

For example:

a) have a repository tree with - $/trunk/
b) $/trunk/ is labeled with 'hit 6.6 release date'
c) $/trunk/ is branched into $/trunk/releases/6.6/

After the fix has been implemented, History for $/trunk/releases/6.6/foo.asm will contain the history for $/trunk/foo.asm to the point of the branch, as well as any labels applied to foo.asm to the point of the branch PLUS the history that occurred after the branch.

Post by **jclausius** » Tue May 18, 2004 9:53 am

minor correct... the above post should read...

c) $/trunk/ is branched into $/branches/releases/6.6/

lawrep · Post by **lawrep** » Tue May 18, 2004 10:02 am

Ah, sorry - I obviously did not understand how the fix would work i.e. that it would indeed be retro-active. That is good news.

Thanks again.

OldMan · Post by **OldMan** » Mon Jun 21, 2004 1:21 pm

I too would very much like to see labels from the source tree displayed in the History of the branch.

(This is not a big deal for us right now, but it will be important in the not-too-distant future.)

lawrep · Post by **lawrep** » Tue Sep 28, 2004 7:29 am

We are about to cut our next release so I was wondering if this problem has been fixed yet? (since 2.0.2)

Thanks,
Paul

Post by **jclausius** » Tue Sep 28, 2004 7:43 am

The current status of this issue is scheduled to be fixed in Vault 2.1.

lawrep · Post by **lawrep** » Tue Sep 28, 2004 7:49 am

Do you have an expected 2.1 release date?

Post by **jclausius** » Tue Sep 28, 2004 8:26 am

As of right now, all I can say is sometime late fall.

SourceGear Support

Vault - Branching does not copy labels

Vault - Branching does not copy labels

Second the motion

Has this been fixed yet?