[Python-Dev] Python 2.6.5
Brett Cannon
brett at python.org
Wed Feb 10 21:56:22 CET 2010
On Tue, Feb 9, 2010 at 21:24, Barry Warsaw <barry at python.org> wrote:
> On Feb 9, 2010, at 4:55 PM, Martin v. Löwis wrote:
>
>>> Le Tue, 09 Feb 2010 12:16:15 +0200, anatoly techtonik a écrit :
>>>> I've noticed a couple of issues that 100% crash Python 2.6.4 like this
>>>> one - http://bugs.python.org/issue6608 Is it ok to release new versions
>>>> that are known to crash?
>>>
>>> I've changed this issue to release blocker. What are the other issues?
>>
>> For a bug fix release, it should (IMO) be a release blocker *only* if
>> this is a regression in the branch or some recent bug fix release over
>> some earlier bug fix release.
>>
>> E.g. if 2.6.2 had broken something that worked in 2.6.1, it would be ok
>> to delay 2.6.5. If 2.6.2 breaks in a case where all prior releases also
>> broke, it would NOT be ok, IMO, to block 2.6.5 for that. There can
>> always be a 2.6.6 release.
>>
>> Of course, if this gets fixed before the scheduled release of 2.6.5,
>> anyway, that would be nice.
>
> I completely agree.
>
Ditto from me.
-Brett
> Besides, unless we have volunteers to step up, create, review, and apply patches, it makes no sense to hold up releases. In the case of the first posted bug, we need a Windows core developer to test, bless and apply the patch.
>
> -Barry
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
>
More information about the Python-Dev
mailing list