This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients christian.heimes, eric.araujo, loewis, ocean-city, r.david.murray, tarek
Date 2010-08-13.17:32:57
SpamBayes Score 1.1338961e-07
Marked as misclassified No
Message-id <1281720779.41.0.0543747046956.issue9558@psf.upfronthosting.co.za>
In-reply-to
Content
Éric, 'release blocker' policy depends on the release manager :)  Barry, for example, likes people to set release blocker on issues they want him to make sure he looks at before the release.  The release manager can always knock it down.  As can other developers if they judge it isn't really a release blocker (unless the RM set it or it was set specifically to get the RMs attention).

When you reset the priority on this one, though, you didn't give it a new priority.  I'm setting it to normal, since the bug report (at the moment at least) is only about a test failure.  If it represents a bug in the ability to build extensions on Windows with VS8, you could raise the priority.
History
Date User Action Args
2010-08-13 17:32:59r.david.murraysetrecipients: + r.david.murray, loewis, ocean-city, christian.heimes, tarek, eric.araujo
2010-08-13 17:32:59r.david.murraysetmessageid: <1281720779.41.0.0543747046956.issue9558@psf.upfronthosting.co.za>
2010-08-13 17:32:58r.david.murraylinkissue9558 messages
2010-08-13 17:32:57r.david.murraycreate