>>>>> On Tue, 9 Sep 2008 02:27:09 -0700, Eric Wilhelm <[EMAIL PROTECTED]> said:
>> I have said it, I have (well, CPAN::Testers::ParseReport has) >> downloaded 56000 reports from >> http://www.nntp.perl.org/group/perl.cpan.testers/ > No, I meant what *testers*. I could tell you but you could find out yourself if you would invest the same amount of time in analysing the results. Sorry, I'm running out of time with this MB release. Schwern is already asking for result for the next Test-Simple alpha. > How are the alpha versions getting > installed? Is it manually, via some option in the automated smoke > tools, or what? I have been under the impression that alpha > dependencies never got installed automatically. Every tester has his own strategy. Mine is to install dev releases and get them tested as such. >> If dev releases pummel other authors it's a call for better tests. If >> your tests are good, then release early, release often and watch the >> results on cpantesters. The point of cpantesters for toolchain >> modules: they may not only watch their own but all test results where >> they might be involved. > How does this process work? If I release an alpha of M::B with a bug, > how long before that irritates, distracts, and confuses a bunch of > other authors? Meanwhile, I have to watch test results for 2000+ other > dists to find it? You can answer this one yourself, right? > What is triggering the testing of dists that use M::B though? Is it > only a newly uploaded dist? How can I tell you. Cpantesters are volunteers and may start today and quit tomorrow. -- andreas
