[python-committers] deferred blockers
Benjamin Peterson
musiccomposition at gmail.com
Sun Sep 14 18:27:37 CEST 2008
More information about the python-committers mailing list
Sun Sep 14 18:27:37 CEST 2008
- Previous message: [python-committers] deferred blockers
- Next message: [python-committers] deferred blockers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Sep 13, 2008 at 10:40 PM, Barry Warsaw <barry at python.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sep 13, 2008, at 9:12 PM, Benjamin Peterson wrote: > >> On Sat, Sep 13, 2008 at 7:37 PM, Antoine Pitrou <solipsis at pitrou.net> >> wrote: >>> >>> Hi all, >>> >>> Now 2.6rc1 is released, shouldn't the issues which have "deferred >>> blocker" status be put back in the "release blocker" category? >> >> I believe most of those issues are actually 3.0 ones that were demoted >> to deferred, so we can release 3.0rc1 on Wednesday. I think the ones >> applicable to 2.6 can be bumped up, though. > > Yes, please bump the 2.6 deferreds to release blockers. I just tried. You'll all be happy to know that we have no 2.6 deferred blockers. :) Maybe, I should bump some other ones up, so we feel stressed enough... -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."
- 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