➜

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 larry, loewis, paul.moore, r.david.murray, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2015-12-22.17:04:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450803849.87.0.276412947886.issue25848@psf.upfronthosting.co.za>
In-reply-to
Content 
Well, it clutters up the buildbot web interface with builders that aren't being used.  Our historical pattern has been to deactivate the builders after a release goes into security-fix-only mode.

Zach, would it be practical to just comment them out and then reactivate them when Larry does a release, or would that eliminate the benefit from your point of view?
History
Date User Action Args
2015-12-22 17:04:09r.david.murraysetrecipients: + r.david.murray, loewis, paul.moore, larry, tim.golden, zach.ware, serhiy.storchaka, steve.dower
2015-12-22 17:04:09r.david.murraysetmessageid: <1450803849.87.0.276412947886.issue25848@psf.upfronthosting.co.za>
2015-12-22 17:04:09r.david.murraylinkissue25848 messages
2015-12-22 17:04:09r.david.murraycreate