bzr 2.2b1 source frozen

[John Arbash Meinel]

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

Martin Pool wrote:
> On 1 April 2010 13:26, Martin Pool <mbp at canonical.com> wrote:
>> The bzr 2.2b1 source is now available from
>> https://edge.launchpad.net/bzr/2.2/2.2b1 and in the process of merging
>> into trunk.  Sorry for the delay.  Please package and test it.
> 
> The merge back to trunk failed because, I think, of a python2.4 issue.
>  It's currently in ~mbp/bzr/integration; I'll try to fix that and
> resubmit it, probably tomorrow.
> 
> Also there seems to be a separate 2.2 branch on Launchpad now.  Do we
> really want that already?
> 

That was my use case for packaging.

Specifically, it can take a while to get a release actually finished.
Several version strings need updating, NEWS needs a final summary, etc.
Plus, once you've finished it, you then need to go back to bzr.dev and
bump *that* up to being N+1.dev.

For a while the Windows packaging built from a branch rather than a tag
as well. And given the vagaries of PQM + tags it still could be
problematic. I generally preferred that the official bzr tag was on the
revision that PQM generated, not on the one *I* generated, even then,
one of the official releases no longer matches the tag in the official
trunk. I found the problem quickly, and wanted to get it bumped, but I
think the LOSAs were extra busy and I didn't push hard enough. I don't
remember the version number now.

Anyway, yes I explicitly wanted a separate branch for a release series.
I thought we were going to do 2.2b1 a while ago, so I had them create it
for me. AFAICT it doesn't actually add any overhead to the release
process. As you still have to create and tag 2.2b1, and then re-open
bzr.dev as 2.2b2-dev. Though I guess you could do both in your offline
branch, have the tag written here, and then pqm-submit the whole thing
in one go?

The fact that your 2.1b1 tarball breaks 2.4 compatibility is a good sign
that maybe we shouldn't be doing it that way.

John
=:->

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

iEYEARECAAYFAku0sjkACgkQJdeBCYSNAAPa9ACfTL1qaJPEqw3ua4/i5bTTgTuP
NaEAoJFTWbMVpmG5YtalL+gtfU/85O7Q
=WPPo
-----END PGP SIGNATURE-----