[Python-Dev] Community buildbots and Python release quality metrics

[glyph at divmod.com]

On 6 Jul, 09:09 pm, grig.gheorghiu at gmail.com wrote:
>On Sun, Jul 6, 2008 at 8:46 AM,  <glyph at divmod.com> wrote:
>>
>>It's one thing to tell people that they need to be helping out (and
>>I'm sure you're right) but it's much more useful to get the message 
>>out that
>>"we really need people to do X, Y, and Z".

>I have posted 'cries for help' repeatedly on my blog, with generally
>little success. See http://agiletesting.blogspot.com/search?q=pybots .
>But I will post again. If you can include here a paragraph of what
>your vision of the 'X, Y and Z' above is, that'd help too

It looks to me like the main thing that Pybots needs is help with 
maintenance.  Getting someone to set up an individual buildbot is one 
thing, but keeping it working is the important bit and it looks like 
people are not doing that.  The project would also be greatly aided by 
having dedicated people diagnose errors, report bugs against Python core 
if they're real and report bugs against Pybots if they're spurious.

It would be good to have this effort be centralized and directed because 
it would otherwise be too easy to file duplicate bug reports, or to 
assume "oh, this has been failing for months, someone must have filed a 
bug already".
>It's not only a question of changing a static label in this case. A
>given buildslave can run the tests for multiple projects, in which
>case it becomes tricky to change the label on the fly accordingly.

I'm a bit confused about how the projects being tested changes on the 
fly... but then, this level of specifics is probably best left to the 
pybots mailing list.  Hopefully sometime soon I'll have the time to add 
yet another subscription.

Thanks for cleaning up the buildbots though!  I can see a lot more tests 
actually running now :).