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 zach.ware
Recipients larry, loewis, paul.moore, r.david.murray, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2015-12-22.17:25:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450805120.08.0.746310355625.issue25848@psf.upfronthosting.co.za>
In-reply-to
Content
Would pretty much eliminate the benefit; there are currently a few special cases for 3.4 (particularly for the ICC builders, and the XP bot), which could go away.

For the record, the secret undocumented method for running a build on all custom builders is to fill out the third-to-last set of entry boxes (the one that includes a "Repo path" box) on http://buildbot.python.org/all/builders and click the associated 'Force Build' button.  It's really not that hard to request such a build, but I will grant that it's rather inconvenient.

On the other hand, it wouldn't be too hard to just add the branch back without the special cases around release time for a little while, but there may be some expected failures.
History
Date User Action Args
2015-12-22 17:25:20zach.waresetrecipients: + zach.ware, loewis, paul.moore, larry, tim.golden, r.david.murray, serhiy.storchaka, steve.dower
2015-12-22 17:25:20zach.waresetmessageid: <1450805120.08.0.746310355625.issue25848@psf.upfronthosting.co.za>
2015-12-22 17:25:20zach.warelinkissue25848 messages
2015-12-22 17:25:19zach.warecreate