firstname.lastname@example.org wrote in message news:20060714051157.29014.803759518.divmod.quotient.35955@ohm...
On Thu, 13 Jul 2006 23:27:56 -0500, email@example.com wrote:
The buildbot idea sounds excellent.
Thanks. If someone can set this up, it pretty much addresses my concerns. ... I am aware of when new releases come out :). What I'm not aware of is what features (may) have broken my code, and why. As long as Python's trunk@HEAD continues to run the test suites cleanly, I am mostly unconcerned. When it breaks, though, I want a chance to look at the cause of the breakage, *before* there is an alpha or beta Python release out and people are starting to write code that depends on its new features.
Is the following something like what you are suggesting?
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 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.
Terry Jan Reedy