[Python-Dev] Python 2.6.5

"Martin v. Löwis" martin at v.loewis.de
Tue Feb 9 22:55:46 CET 2010

> 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.


More information about the Python-Dev mailing list