Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I've also been thinking about this recently, but have yet to think of a suitable solution. While the dev release testing is useful for authors, it isn't for users who don't expect to ever use those releases in a production environment. This applies to past developer releases 5.9.x and 5.7.x, as well as 5.11.x. Incidentally was 5.5.x a developer release?

    In the future with the newer system that's in production, it will hopefully be easier to filter these releases out. However, at the moment, the CPAN Testers

    • Personally, I'm quite happy for the statistics site to keep including developer releases, at least in the headline graphs.

      For the version/platform matrix, that's where I'd like to see you remove dev Perls
  • I see your point. This level of intensity in testing is great for the Perl core -- I would love to get it for Parrot -- but less useful for non-core distributions.

    Since the testers responsible for these dev versions are (a) our #1 tester (by volume) and (b) one of our most respected module authors, perhaps this could be raised on the CPAN Testers Discussion list -- which they both read -- and a proposal for change worked out.