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.
  • by dagolden (6584) on 2009.03.30 17:04 (#67957) Journal

    You left off that Tux released Config::Perl::V [], which provides structured information from 'perl -V' -- including things that aren't available from

    To clarify the CPAN Testers evolution, at least from the client perspective:

    Stage 1: Test::Reporter::Transport::Metabase will soon be available as a means to submit test reports to a CPAN Testers Metabase using existing clients (CPAN/CPAN::Reporter or CPANPLUS/CPAN::YACSmoke) that support Test::Reporter::Plugins. The reports will still be primarily the same text report as exist today, augmented with any structured data that can be parsed out of the report using tools from Andreas and Tux.

    Stage 2: CPAN Testers report generation and submission will be consolidated from CPAN/CPAN::Reporter, CPANPLUS and Test::Reporter into a new CPAN::Testers::Client module that communicates with a CPAN Testers Metabase. There will be adaptors specific to CPAN and CPANPLUS to deal with slight variations in how they each provide information about distributions being tested. (Jos and I hammered out the future API for the client on Sunday.)

    As CPAN and CPANPLUS are upgraded to use the new client instead, the current use of CPAN::Reporter/Test::Reporter will be removed and CPAN Testers will be only be using the Metabase infrastructure, not email submission with NNTP archives. These reports will be entirely structured data and the old textual report will not be generated.

    Stage 3: When enough testers are switched over and the system has a shakedown period, a date to retire the email list will be announced.

    -- dagolden