This week in PSC (175) | 2025-01-09

Three of us again. Aristotle had limited time, Philippe and Graham stayed longer.

  • Steve Hay released the RCs for for 5.38.3 and 5.40.1. Thank you!
  • Philippe rebased his Perl 42 branch on top of blead after the release of v5.41.7. Things are on track to build a 41.8 testing tarball alongside the 5.41.8 release and we will keep this dual track going for now. We agreed that if we decide to go through with the 42 plan, we must have at least three 41.x-only releases, to keep with the feature freeze policy.
  • We also considered the behavior of use VERSION when given a non-existent version from the gap between the last v5.41.x and 42. We think it should be an error, to continue helping with typos (in line with the current helpful error message when requesting e.g. 5.10 instead of 5.010).
  • We talked about forbidding non-overloaded references stringification. Everyone seems in agreement that the feature is good to have, but the way to enable it is less clear for now: it could be a stricture, warning, feature flag, or pragma.
  • We briefly touched on feedback on our preliminary plan for TLS in core, suggesting that an even simpler approach may be possible. We will pick this back up in a future call.

[P5P posting of this summary]

This week in PSC (174) | 2025-01-02

Just Aristotle and Graham for our first meeting of the new year. Not much progress since the last one due to Christmas, New Year’s, sickness, and other personal circumstances. We discussed our framing of the version bump, the timeline for a decision, and the fact that constraints push us toward a dummy .0 third version component as the simplest way forward.

[P5P posting of this summary]

This week in PSC (173) | 2024-12-20

For the last meeting of the year we were all present again.

  • We have requested further input regarding our plan for TLS in core.

  • We picked the ball back up that we dropped regarding point releases. They should be coming soon.

  • We went over our findings so far regarding Perl 42. It looks like Perl versions will have to continue to be written with three components, so we will be stuck with a fixed .0 at the end. It’s slightly annoying, but we can live with it. We strategized about how to get more real-world data about feasibility, and discussed the possibility of releasing a perl-41.8 tarball alongside the regularly scheduled perl-5.41.8.

[P5P posting of this summary]

This week in PSC (172) | 2024-12-12

All three of us attended.

  • We discussed the version 42 work on the psc/ppc0025 branch. We have an initial proof of concept that is almost good enough to test against CPAN in order to assess whether the plan is actually feasible and proceed from there. We discussed the timeline for this.
  • We reviewed our plan for TLS in core. Some questions came up based on the conversation on the p5p thread and we need specific next steps now that Craig has provided a patch for the first one. We hashed out next steps to keep this moving.
  • We briefly discussed the Random::Simple suggestion and decided we won’t address it at this time. (The inclusion of cryptography libraries in core will probably change the situation here in the foreseeable future.)

[P5P posting of this summary]

This week in PSC (171) | 2024-12-05

This week felt like a PSC reunion meeting. We extended invitations to join us for a discussion of the version change to a number of core contributors, and ended up joined by ex-PSC members Ricardo and Paul (Neil would have joined, but couldn’t make it).

There is skepticism but no strong opposition. The benefits are in some doubt, and resources to implement this will not come from core contributors. So we want to experiment on a branch to get a handle on feasibility and viability, which we hope will give us better data to evaluate the proposal and, we hope, allay any worries.

We also briefly discussed our intentions for the PPC process with Paul. We are thinking about an automatically generated status page on GitHub Pages.

[P5P posting of this summary]