This week in PSC (198) | 2025-07-04

All three of us attended.

  • We reviewed the perldelta entry for the CVE-2025-40909 patch, which has so far been blocking the security point releases. We reasoned out previous tentatively assumed necessary improvements to the text and ended up rejecting them and concluding that the text is perfectly adequate. The point releases can now go ahead.
  • Philippe reported on the experience with the release process and thoughts on how to improve it and the release guide. Main takeways are that it would be useful to have a single source of truth for the version of Perl (e.g. for buildtoc) and that what we think of as the release process is really a procedure for performing a state transition on the repository, where the repository constitutes the input to makerel, and the state transition aims to trigger the correct change in the output of makerel.
  • We initiated transition to next PSC and discussed preparations for passing on an agenda for continuity.

[P5P posting of this summary]

This week in PSC (197) | 2025-06-26

All three of us attended.

  • The release is imminent while Chris Williams, who usually releases Module::CoreList, is temporarily absent. We were not all sure whether this would require any additional coordination. Phillipe had sent mail to clarify the situation. We concluded that there is no issue because CoreList is an outlier: it is not upstream-CPAN but neither is it upstream-blead, while nevertheless being maintained in core. A lagging CPAN release won’t be a problem, even though that’s not the usual sequence. In the event, Chris responded to the mail with assurance that he is available enough anyway.
  • We coordinated further about the release, which is coming up the following week.
  • Release blocker triage this week ended as it began: with no blockers.

[P5P posting of this summary]

This week in PSC (196) | 2025-06-19

Graham couldn’t make it, so only Aristotle and Philippe this week.

  • We discussed the structure of the feature.pm documentation and how unfeatures should be covered. Philippe has provided a first patch which extends the description of each unfeature with a note stating from which feature bundle onward it is disabled.
  • Relesae blocker triage continues. The meeting began without any unresolved blockers and ended the same way.
  • Philippe plans to ship 5.42.0-RC1 as soon as the last missing perldelta entries are in.

[P5P posting of this summary]

This week in PSC (195) | 2025-06-12

All three of us attended.

  • Release blocker triage yielded no new blockers. We followed up on the issues we were already tracking.
  • The security release made some progress this week, but has been held up by the lack of a perldelta entry.

[P5P posting of this summary]

This week in PSC (194) | 2025-06-06

All three of us attended.

  • Release blocker triage continues. Several more blockers have been resolved. We identified no blockers among new tickets but did consider #23346 and may ship it even if we do not consider it a blocker.
  • We discussed some feedback regarding the fix for CVE-2025-40909 and requested that the patch be amended. A perldelta entry is also missing before we can ship the security releases.
  • We discussed who will do then stable release and when. RC1 will be published by Philippe Bruhat on June 20th.
  • We went over the scalar-context pair constructor proposal. Changing the fat arrow in general is out of the question and we don’t think any other proposal is likely to work.
  • We went over the 2-arg open proposal. It seems mostly trivial to do and worthwhile as well, but the real complexity is in the implicit open done by readline. We will outline our thoughts on the thread.

[P5P posting of this summary]