[MERGE] Tagging bzr releases
John Arbash Meinel
john at arbash-meinel.com
Tue Feb 10 19:38:36 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Jelmer Vernooij wrote:
> The attached patch updates releasing.txt to mention tagging of the
We've never had a policy of tagging releases. I've done it ad-hoc in my
There is still something wrong about how PQM manages things, in that the
tags aren't getting propagated from branches that get merged, into the
trunk. Though I haven't tried since we upgraded bzr.dev to 1.9 format
(which also, IIRC, required updating the bzr used by PQM).
Anyway, I've always used tags of the form:
rather than just "1.12rc1".
Other projects (bzrtools, qbzr) use "release-1.12rc1". bzr-svn seesm to
use my form: "bzr-svn-0.4.9" (though bzr-svn-0.5.0~rc1).
Obviously, I have a preference for "$PROJECT-$VERSION". It isn't strong
enough, but consistency here would be nice.
In the end:
1) I'd like to officially tag releases.
2) It is a bit tricky, because you really want to create a tag at the
tip of the branch, which you can't do until after PQM has finished
committing. And then we don't have a way to inject that tag back into
the release branch it exists on. We *can* inject that tag into bzr.dev
when we merge the release back into trunk.
3) Martin didn't actually get the 1.12rc1 changes submitted (and
accepted) through PQM, he released from a local branch (I assume). I
went ahead and applied the changes and submitted them for 1.12rc1
because I needed them to get the win32 installers built.
Basically, I like the idea, but I think the actual actions are
incomplete. We need to settle on a tagging/naming scheme, and then the
instructions need to be updated to figure out how to get these tags back
into the system.
Note that normally my release branches are checkouts of
"http://bazaar-vcs.org/bzr/bzr.$VERSION", which means that "bzr tag"
fails because it cannot update the tags for an HTTP branch. The way *I*
do it is:
bzr tag -r branch:../releases/bzr.1.12 bzr.1.12rc1
Note that this normally means I'm creating a tag on a revision which
isn't (yet) even in that branch, it works because the rev is in the
repository, because "releases" is under the same shared repo. (And in
theory, I could do it as part of merging the changes back into bzr.dev,
wherein they *could* be in that branch.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar