tags in bzr.dev

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

>>> I also see that there seem to be no tags at all for 1.13 and 1.14.
>> I believe there is an as-yet undiagnosed problem with propagation of
>> tags through pqm.  (Robert may know more.)  I'm not sure why there are
>> some tags and not others.
> 
> 
> You can't tag a release until PQM has finished merging, testing, and
> committing it. So you can't have a release tag "right away".

So I'm somewhat wrong about this. 'jml' added a bzr-1.16 tag to *his*
copy before he submitted it to PQM, rather than setting it on the
"official" revision that resulted from the merge. We should certainly
decide as a project which tag method we prefer. It is nice to get a
'bzr-1.16' tag into the 'bzr.1.16' branch, though having it be:

- ------------------------------------------------------------
revno: 4437 [merge]
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: 1.16
timestamp: Thu 2009-06-18 12:29:22 +0100
message:
  (jml) Prepare 1.16.
    ------------------------------------------------------------
    revno: 4436.1.1
    tags: bzr-1.16
    committer: Jonathan Lange <jml at canonical.com>
    branch nick: prepare-1.16
    timestamp: Thu 2009-06-18 20:29:00 +1000
    message:
      Release 1.16.

Is a bit strange, though not terrible. (Also a bit funny that 'Prepare
1.16' was the official commit message.)


Ah, it seems that 1.16 final was never merged back into trunk, which is
why we don't have the tag there. I'll go ahead and do it.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko/lb0ACgkQJdeBCYSNAAM0fwCfXlmj8qj6JfQvyUF+2AhRx3/S
nggAniagk2QiyS1Ub1CbE2f7SvC8/QBt
=Axgt
-----END PGP SIGNATURE-----