Status for release branches

[John Arbash Meinel]

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

I'm thinking we probably want to make the official release branches
marked as "Mature" so that they show up at:
  https://code.edge.launchpad.net/bzr

However, as the branches are owned by ~bzr-pqm, I don't have rights to
change their status. I'm guessing that to give rights to change the
status of a branch, you have to have writes to *push* to the branch,
which we don't want to do.

Any ideas?

The current case is that once a branch has been 'merged up' and brought
back into core, the branch listing disappears, so only the
release-series branches are shown. (so lp:bzr and lp:bzr/2.0, but none
of the ~bzr-pqm/bzr/{2.0.1,2.0.2,2.1.0b1,2.1.0b2} will be shown once I
finish doing all my merging.)

Do we think showing these branches as 'Mature' on the bazaar branches
page would be useful? What about just showing the 'latest' ones and
marking the rest as merged. (So 2.0.2 will be shown, but not 2.0.1)

John
=:->

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

iEYEARECAAYFAkrvScIACgkQJdeBCYSNAANOFwCgzwbLXCMHXKvXhETJGlUM2Brk
FIUAn2zruOrA+vtnYmmIxFDrtA7opZPF
=N1Xc
-----END PGP SIGNATURE-----