On Sat, 15 Jul 2006 00:13:35 -0400, Terry Reedy firstname.lastname@example.org wrote:
Is the following something like what you are suggesting?
Something like it, but...
A Python Application Testing (PAT) machine is set up with buildbot and any needed custom scripts. Sometime after that and after 2.5 is released, when you have a version of, for instance, Twisted that passes its automated test suite when run on 2.5, you send it (or a URL) and an email address to PAT. Other developers do the same. Periodically (once a week?), when PAT is
^ "once per checkin to Python trunk"
free and a new green development version of either the 2.5.x or 2.6 branches is available, PAT runs the test suites against that version. An email is sent for any that fail, perhaps accompanied by the concatenation of the relevant checkin message. Some possible options are to select just one of the branches for testing, to have more than one stable version being tested, and to receive pass emails.
Sending email also isn't really necessary; I would just like a web page I can look at (and draw the attention of the python core developers to).