> On Oct 17, 2017, at 1:06 PM, Doug Bell <[email protected]> wrote: > > >> On Oct 14, 2017, at 8:34 AM, James E Keenan <[email protected]> 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.
Doug, Thanks for the reply. I proposed this idea originally. Essentially the thought was to use the data already there to hint to p5p there might be a problem worth digging into. The alternative would be to build Yet Another Smoking System. In accordance with the 3 great virtues, I'm way too lazy for that. What needs doing to make this a "report" of sorts that could be dug through by interested parties? Are we just talking about a flat file that a perl release manager could update which would provide this information to whoever? Thanks, Todd
