Barry Warsaw barry at python.org
Mon Sep 15 15:34:48 CEST 2008

• Previous message: [python-committers] deferred blockers
• Next message: [python-committers] deferred blockers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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

On Sep 14, 2008, at 12:58 PM, Martin v. Löwis wrote:
>>
> I thought this was the plan from the beginning: make sure that for  
> rc1,
> there aren't any blockers - not even deferred ones. All 3.0 blockers
> got deferred before 2.6rc1, but the 2.6 blockers stayed.
>
> In case you wonder where they all went - I "resolved" a number of them
> by declaring that they shouldn't really block the release; in most
> cases, people then agreed (or didn't object).
>
> As a criterion, I asked "could that get fixed in 2.6.1 as well?", and
> I thought it could if
> - it's not a regression wrt. 2.5, and
> - it's not really that embarrassing, and
> - fixing it won't violate the policies that we had established for
>  bug fix releases.

Martin, I agree with your take on this, and Guido's follow up.  Thanks.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSM5keHEjvBPtnXfVAQIGugQAkYDZatppkBTysc1+wJ1raamgBdIqFXA/
+/jUiEv6dRHIhfu+CqAhCD+M8h5sWl2iZ+VZaHqvgiJdv7nU1Zd+oQCp4Iw42rOP
Eqy/bR1euBO3tQxqrq5UyFVZjCuYEIvwJP0odiFoa/ygc7J7/yuu2EEysG97Xgo7
urZRlZO2UGw=
=T3PN
-----END PGP SIGNATURE-----

---

• Previous message: [python-committers] deferred blockers
• Next message: [python-committers] deferred blockers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list