bzr-2.3.2, SRU and conflicting tags

[John Arbash Meinel]

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

On 5/12/2011 11:12 PM, vila wrote:
> Hi guys,
> 
> I was cutting the 2.3.2 release and encountered an issue:
> 
> * I created the bzr-2.3.2 tag and submitted to pqm (lp:bzr/2.3) (yeah,
>   for once I didn't run the test suite locally, shame on me !)
> 
> * I ran make check-dist-tarball | subunit2pyunit and got > 1000
>   failures... Hello http://pad.lv/760435 ! Of course, pqm running py2.6
>   happily ignored the problem (and of course this patch landed while I
>   was in vacations and babune wasn't running so I never witnessed the
>   bug nor realized the implications).
> 
> * I thought that the SRU won't be possible without a passing test suite
>   (oops ?)
> 

Why is the SRU running python 2.7? If we are backporting to Natty, I
thought that still had a default of python 2.6. (I certainly could be
wrong.)

I would personally say, if python2.7 is the target, and Natty can't pass
the test suite, then we fix it for bzr-2.3.3 and don't try to SRU 2.3.2.
The release *is cut*, the tarballs are in the wild. Now is *not* the
time to override the version.

We can cut bzr-2.3.3 *today* if you want, but the ship has long since
sailed for us to release something new called bzr-2.3.2.

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

iEYEARECAAYFAk3MyXEACgkQJdeBCYSNAAOk5QCfVM1jiQ9cDr4TeNUCiWH4ZsEg
FkQAnRtve/QVP1LS72J0fV7fIu9JD6zh
=f32R
-----END PGP SIGNATURE-----