[Python-Dev] 3.3 release plans

[Nick Coghlan]

On Mon, Jun 25, 2012 at 6:14 AM, Eric V. Smith <eric at trueblade.com> wrote:
> On 6/24/2012 11:44 AM, Eric V. Smith wrote:
>> On 6/24/2012 11:27 AM, Antoine Pitrou wrote:
>>>> What's your timeframe for bug fixes today? I'd very much like to fix
>>>> http://bugs.python.org/issue15039, but it will probably take me another
>>>> 2 hours or so.
>>>
>>> If it's a bugfix, it's not blocked by the feature freeze at all: you
>>> can commit after beta (but you might want the bugfix to be in the beta).
>>
>> Indeed, that's what I'm after: the fix in the beta. I'll do my best to
>> get it in, but obviously it's not a blocker.
>
> And, no surprise: it's harder to fix than I thought. It won't make it in
> to the beta.

FWIW, the way I'll often handle that kind of change is to temporarily
set it to "release-blocker" (so the RM will at least look at it before
deciding whether or not to proceed with the release), and then drop it
down to "deferred blocker" if I decide it's not going to be ready, but
want to commit to getting it fixed before the *next* release.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia