This week in PSC (144) | 2024-04-11

The three of us met, and:

  • merged the deëxperiment PR
  • agreed we should additionally discuss if the now-stable features (try, extra_paired_delimiters) should be included in the :5.40 feature bundle
  • reported feedback from PPC implementors, which can be summarized as “life happened, will get back to work soon”
  • continued to triage latest reported bugs and look for release blockers (Currently we have 8 potential blockers, though 2 are easy documentation fixes)

This Week in PSC (143)

  • We’ll chase up current implementors of outstanding PPCs to see what progress is
  • Reviewed the new bugs since last review. One new potential blocker - 22121
  • Reviewed a first draft of a “Perl Roadmap” presentation that might be given at PTS

This Week in PSC (142)

  • Discussed some specific ideas for future perl development - more ways to allow CPAN modules to experiment with new ideas, import some possibly-stable ideas from CPAN into core.

  • Reviewed the list of ongoing experiments in perlexperiment.pod to work out what can now be declared stable. We’re technically past “user visible changes” freeze but maybe the list will be happy with these changes anyway.

  • Observed that SSL-in-core still hasn’t made any progress, and wondered further on how we can unstall it and try to get someone working on it eventually. Maybe writing a PPC doc would help?

This week in PSC (141) | 2024-03-21

This week, we:

  • Talked about some ideas for discussion at the upcoming PTS
  • Discussed the current blocked state of bleadperl following the 5.39.9 release and how to unblock it
  • Finished reviewing the release blocker bugs
  • Discussed how MetaCPAN should better handle perl releases and permissions

PSC #140 2024-03-14

This week, we discussed:

  • Further look down open bugs to tag some as being release-blocker
  • Do we want to revert PR21915? - discussed in its own email thread
  • Thought of a couple of issues to discuss with the wider group at the upcoming PTS
    • How to handle “important author is AWOL” for upstream CPAN issues
    • How to not break CPAN tests when adding new warnings to core