on moving tags

[Martin Pool]

On 17 May 2005, Lalo Martins <lalo at exoweb.net> wrote:
> I think I came up with the solution for moving tags.  See if I make
> sense.
> 
> 
> 1.  Tags are not versioned.  They're not part of the "source".  They are
> branch metadata.
> 
> 2.  Each tag is associated with a *list* of revision (numbers or uids, I
> haven't thought about that).
> 
> So when you go `bzr pull -t stable $branch`, you get the latest revision
> associated with the tag "stable".
> 
> Let's say the latest stable is 50, and you test it and it doesn't work
> for you.  You want the previous one.  Then you go `bzr pull -t stable<50
> $branch`.  Conversely if you are at 23 and want the *next* stable, you
> can go `bzr pull -t stable>23 $branch`.
> 
> The command line syntaxes are of course open to debate... er I mean,
> even more so than the rest of the idea.

This seems like a variation on the plan laid out in tagging.txt.  That
would have tags also representing a list of versions, but you can pick
from within that list by using sub-versions of the tag: 

  bzr diff -r stable            most recent "stable"
  bzr diff -r stable.2          second tag of "stable"

On the whole though, I think I'd encourage people to have a branch
called "stable" and merge in to that, rather than having a tag that
gets moved all the time.  Tags are a point in time and should be moved
basically only when you make a mistake; code that develops and changes
should be on a branch.  (But this is only a recommendation, not
something we should enforce.)

-- 
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050517/61b626b8/attachment.pgp