RM responsibilies: Creating a new code branch?
John Arbash Meinel
john at arbash-meinel.com
Mon May 4 22:04:52 BST 2009
-----BEGIN PGP SIGNED MESSAGE-----
Bob Tanner wrote:
> Is it the RM's responsibility to create a new code branch?
> I created the
> 1.15 series (https://launchpad.net/bzr/1.15)
> as well as the
> 1.15rc1 Milestone (https://launchpad.net/bzr/+milestone/1.15rc1)
> what's missing is the code branch, ala
> https://code.launchpad.net/~bzr/bzr/bzr.1.15 (not valid link at this time)
> Is creation of the code branch the RM's responsibility? If so, it's not
> documented in the releasing docs. Poking around I believe I have the
> procedure to create the code branch but I want to make sure I'm not
> stepping on toes if I go ahead and create the branch.
> If it's the RM responsibility I'll RFC documentation on how I believe a
> code branch should be created.
Generally, Robert is the only one that makes the final release branch.
And he does so just before release, because it is a direct branch off of
bzr.dev. He then sets it up to be managed by PQM. (He does it as he is
one of the few people that have rights to set things up for PQM.)
If we made it early, then we would have to take care to land things 2
times that we want to be in 1.15. At least, we try to make an official
release as close to a simple tag of trunk as we can. Barring the obvious
internal numbering changes, etc. Of course, the last releases have shown
that we aren't quite there yet.
-----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