On Thu, Sep 4, 2008 at 5:39 AM, David Golden <[EMAIL PROTECTED]> wrote: > On Wed, Sep 3, 2008 at 7:18 PM, Barbie <[EMAIL PROTECTED]> wrote:
>> Another irritation for authors is to receive reports for distributions >> that have since been fixed. This has been much more of a problem in >> recent times as many of the testers have recently built new environment >> and are testing all of CPAN. I don't see the value of sending authors >> reports for distributions that have since got a PASS report. This is > > If you mean don't test 1.01 when 1.02 has a PASS, then I agree. My > approach with CPAN::Reporter::Smoker is to test only the latest > release -- even if "latest" was 5+ years ago. I think we should > discourage testing older distributions entirely. > > Note that this is potentially something that we could "enforce" by > checking if a distribution is no longer the most current and > discarding reports that refer to older releases. But that's tricky > logic and I'd rather defer that until we have more centralized > control. I partially disagree here. I would not send any new report to authors about old versions of their modules but I would like to see them collected and displayed. I think CPAN Testers already has a lot of value to ordinary users as well and not only to authors. I'd like to preserve this value and even increases it. We all have workplaces and clients with old versions of perl. Barbie just wrote about using 5.8.0, I have two clients using 5.6.x. As some of the modules don't work on those platforms in their latest version people will have to find the older version. For that they will need to find the latest version with a PASS report. So I think it is important to collect new reports - at least PASS reports - on older versions of a module. Actually I would not suppres FAIL reports either as seeing those in higher versions of the module helps the confidence that we found the latest working version of the module: When you see a PASS on 0.03, no reports on 0.04-0.99 and a FAIL on 1.00 you still have to go through all the versions in between to find out if 0.03 is really the newest that works? Imagine Barbie needs to do that for a module but all is FAIL reports are discarded. Next time David has to through it again. I'd rather see these reports collected but in order not to annoy the authors, don't report them in either e-mail or rss or any other way Gabor
