
It's about time for another 3.1 bug fix release. I propose this schedule: March 6: Release Candidate (same day as 2.7a4) March 20: 3.1.2 Final release -- Regards, Benjamin

Stefan Behnel wrote:
Benjamin Peterson, 13.02.2010 03:52:
It's about time for another 3.1 bug fix release. I propose this schedule:
March 6: Release Candidate (same day as 2.7a4) March 20: 3.1.2 Final release
Does a crash like #7173 qualify as a blocker for 3.1.2?
I'm not the release manager, but my feeling is that, because there is no proposed resolution of the issue, it can't possibly be a blocker. Only if a patch is available, waiting for application of that patch may block the release. Waiting for a patch may cause indefinite delay, which would be bad. Of course, for releases managed by Barry (i.e. 2.6), Barry said that you can declare anything a blocker - whether it then will block the release is a different matter (and one that Barry then decides on a case-by-case basis). Regards, Martin

2010/2/15 "Martin v. Löwis" <martin@v.loewis.de>:
Stefan Behnel wrote:
Benjamin Peterson, 13.02.2010 03:52:
It's about time for another 3.1 bug fix release. I propose this schedule:
March 6: Release Candidate (same day as 2.7a4) March 20: 3.1.2 Final release
Does a crash like #7173 qualify as a blocker for 3.1.2?
I'm not the release manager, but my feeling is that, because there is no proposed resolution of the issue, it can't possibly be a blocker. Only if a patch is available, waiting for application of that patch may block the release. Waiting for a patch may cause indefinite delay, which would be bad.
I agree with Martin here. I would be more inclined to make #7173 a release blocker if it had a more specific test than "run cython and maybe it'll crash". -- Regards, Benjamin

Hi, 2010/2/15 Benjamin Peterson <benjamin@python.org>
2010/2/15 "Martin v. Löwis" <martin@v.loewis.de>:
Stefan Behnel wrote:
Benjamin Peterson, 13.02.2010 03:52:
It's about time for another 3.1 bug fix release. I propose this schedule:
March 6: Release Candidate (same day as 2.7a4) March 20: 3.1.2 Final release
Does a crash like #7173 qualify as a blocker for 3.1.2?
I'm not the release manager, but my feeling is that, because there is no proposed resolution of the issue, it can't possibly be a blocker. Only if a patch is available, waiting for application of that patch may block the release. Waiting for a patch may cause indefinite delay, which would be bad.
I agree with Martin here. I would be more inclined to make #7173 a release blocker if it had a more specific test than "run cython and maybe it'll crash".
I just updated #7173 with a short crasher. In short, I think that next() in an exception handler messes with the exception state. This doesn't play well with the cyclic garbage collector which can call tp_clear() on a resurrected object, if the reference is *moved* out of the cycle by some tp_dealloc. -- Amaury Forgeot d'Arc
participants (5)
-
"Martin v. Löwis"
-
Amaury Forgeot d'Arc
-
Antoine Pitrou
-
Benjamin Peterson
-
Stefan Behnel