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 eric.smith, mark.dickinson, python-dev, r.david.murray, skrah, yaubi
Date 2014-08-27.14:00:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409148054.3.0.172008237155.issue22090@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not going to argue this any further, but "recent" is exactly the point...if all of the bots had turned red you'd understand that it needed to be fixed *immediately* or the triggering change (regardless of what the actual bug was) backed out.  Since it isn't all the bots it isn't that critical, but eventually we want to make it critical (ie: someday it will be a requirement that *all* stable bots pass before a change gets *committed*...but that day is still a longer way off than I'd like, since I at least don't have much time for working on the workflow stuff).
History
Date User Action Args
2014-08-27 14:00:54r.david.murraysetrecipients: + r.david.murray, mark.dickinson, eric.smith, skrah, yaubi, python-dev
2014-08-27 14:00:54r.david.murraysetmessageid: <1409148054.3.0.172008237155.issue22090@psf.upfronthosting.co.za>
2014-08-27 14:00:54r.david.murraylinkissue22090 messages
2014-08-27 14:00:54r.david.murraycreate