> On Oct 14, 2017, at 8:34 AM, James E Keenan <jkee...@pobox.com> wrote: > > Would it be possible to generate a monthly report from data in the > CPANtesters database(s), identifying all CPAN libraries: > > (i) which had not had a new version uploaded to CPAN in the past month; but > > (ii) which had experienced new breakage in their test suites in the past > month -- breakage which could hypothetically be attributed to a change in the > Perl 5 source code from one monthly development release to the next? > > I realize that that question is probably not yet precise enough to be > translated into a database query. However, we welcome your insights into how > CPANtesters data can be leveraged for the benefit of better Perl 5 core > development.
It seems like what you want is: 1) All the CPAN distributions that have not had a new release in 1 month 2) AND have at least 1 PASS report against the latest stable Perl release 3) AND have at least 1 report against the latest dev Perl release 4) AND have 0 PASS reports against the latest dev Perl release CPAN Testers can do _almost_ all of that right now using the data we have, except for "What is the latest stable Perl release?" and "What is the latest dev Perl release?" Adding that data dovetails nicely with the existing problem of the Perl version list on CPAN Testers is out of date.
signature.asc
Description: Message signed with OpenPGP
