On Feb 9, 2010, at 5:20 PM, Martin v. Löwis wrote: > Of course, the release manager can always declare anything a release > blocker, so that may have been the reason (I don't recall the details).
I should probably clarify my last statement. I will sometimes mark an issue "release blocker" because I'd really like it to be fixed for the next point release, or because we're very close to having an applicable patch. Think of it more as a reminder to address the issue before the next release is created. However, I have also knocked issues down from blocker if it's clear that we won't have a fix in time, and it meets the other criteria that Martin has laid out. So feel free to mark issues as release blockers for 2.6.5. That doesn't mean it will actually block the release. -Barry _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
