New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Perl development release dashboard (Bleadperl Breaks CPAN) #12

Open
preaction opened this Issue Nov 28, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@preaction
Member

preaction commented Nov 28, 2017

As part of the Perl 5 development process, the modules on CPAN are tested against the latest development Perl 5 version. If tests fail, they are used to track down the commit in Perl 5 that caused the failure so that it can be fixed. This called the Bleadperl Breaks CPAN project, and is a common occurrence on the Perl 5 Porters mailing list.

To make this process easier, it would be nice to make a web-based report of CPAN distributions that are possibly broken by the latest development Perl 5 release. This list should consist of CPAN distributions that:

  1. ... 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

This should be implemented as a new controller, CPAN::Testers::Web::Controller::PerlSmoke. It should have one page that creates a table of:

  1. Distribution
  2. Distribution version
  3. Last passing Perl version
  4. Last failing Perl version

Clicking on the distribution should open an expanded view that displays a list of the reports for the user to click through to see the full text. Each report list item should show:

  1. Report ID
  2. Reporter name
  3. Perl version
  4. OS name / version
  5. Date/time of the report

This is part of our beta features program, and should be listed in share/templates/index.html+beta.ep with a link to the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment