March 2026 Archives

This week in PSC (219) | 2026-03-30

All three of us attended.

  • We discussed policy questions that were turned up by the recent submission of some LLM-generated PRs. We need to hold conversation about this among the Core team. No contributions of this kind will be accepted while the discussion is still ongoing.

  • We finally had a good chunk of time to spend on release blocker triage. We made quick progress, working through half our list and closing some issues in the process. We newly marked 4 issues as blockers.

[P5P posting of this summary]

This week in PSC (218) | 2026-03-16

All three of us attended this long meeting covering quite a bit ground:

  • CVE-2026-3381 obliges us to cut a 5.42.2 point release with an updated Compress::Raw::Zlib.

  • We accepted Philippe’s and Eric’s offer to handle the last dev releases of the cycle.

  • Olaf Alders requested more explicit EOL notices and has updated perlpolicy.pod and the release manager guide accordingly. We agreed that the release announcement mails for the final dev release and the stable release should also contain a brief note about the perl version which is falling out of support, and filed an issue to make this happen.

  • We sent mail to kick off the voting process for some new core team member candidates.

  • We discussed the state of Devel::PPPort. It has been outdated for some time and needs to be unstuck.

  • We would like to get customize.dat down to the only entry that cannot be removed (for version.pm). We will try to coordinate with maintainers.

  • We noticed that we missed the deprecation of multiple use VERSION declarations in the same scope, which was supposed to be fatalized in 5.44. It is too late now to do that in this dev cycle, so the warning will have to change to 5.46 and the deprecation revisited next cycle.

  • Further on the topic of overlooked deprecations, we considered how to prevent this from continuing to happen. We decided that some kind of documentation of recurring PSC obligations during a cycle is needed, which would also include things like the contentious changes freeze and release blocker triage.

  • There was not much time left for release blocker triage, so we only did a little, which surfaced no candidate blockers so far. (A few already-definite blockers have been spotted and marked outside of triage.)

[P5P posting of this summary]

This week in PSC (217) | 2026-03-09

All three of us were present for a quick meeting.

  • We discussed the progress of our outreach to some potential new core team members. We will be holding a vote once we hear back from everyone.

  • We noticed that a minor step in the PSC transition was missed during this cycle. We agreed that there needs to be a checklist for the procedure, and we intend to write it up.

  • We started with the release blocker triage, but the meeting was short so we didn’t look at many issues. We have no candidate blockers so far.

[P5P posting of this summary]

This week in PSC (216) | 2026-03-02

After two weeks of various people absent on various travels, we got the band back together for a fairly adminstrivial meeting.

  • Contentious changes freeze has set in, so we will now be monitoring for release blockers. We took stock of the currently open issues and PRs from this release cycle and will be triaging for blockers in the coming weeks.

  • We need release managers for two more dev releases and the final. Paul will probably take over one of the dev releases. We are figuring out the rest.

[P5P posting of this summary]

About Perl Steering Council

user-pic