2010/2/15 "Martin v. Löwis" <martin at 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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4