The transition meeting to the new PSC proved a bit tricky to schedule to get everyone from both the old and new PSC in attendance, but eventually we succeeded: Aristotle, Graham, Leon, Paul, and Philippe all participated.| blogs.perl.org
Only Graham and Philippe attended. We coordinated with Aristotle via chat. | blogs.perl.org
All three of us attended.| blogs.perl.org
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...| blogs.perl.org
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.| blogs.perl.org
All three of us attended.| blogs.perl.org
All three of us attended.| blogs.perl.org
We caught up on release blocker triage. We are tentatively all clear: all previously identified release blockers are now resolved, and there were no new blockers in recent issues and pull requests – except possibly a 32-bit Windows build issue we are not yet certain about. We are keeping an eye on that.| blogs.perl.org
All three of us attended.| blogs.perl.org
We were all present. The status of smartmatch came up. It is in a weird position where it used to be part of the language, then was retroactively declared an experiment, then deprecated and slated for removal, and now it’s...| Perl Steering Council
A meeting with full attendance. We caught up with new issues and pull requests without finding any new release blockers. We went over the state of the perldeprecation and perlexperiment POD pages. We found that perlexperiment does not yet reflect...| Perl Steering Council
Release blocker triage continued, across two days. First we caught up with a dozen of new issues and pull requests, of which we identified one more PR as a small release blocker. The majority of our time was then spent considering each release blocker in depth and updating tickets with decisions and/or requests as we went along. A number of small blockers got resolved even during the course of our extended meeting.| blogs.perl.org
All of us showed up for a long meeting of identifying release blockers. First we went over the issues and PRs submitted since last week, none of which turned out to be new potential blockers. Then we examined all of the issues and PRs of interest we had previously identified. We applied the “Release Blocker” label where necessary, left comments, and merged a few of the PRs. Out of 20 issues and 11 PRs on our list, we identified 5 issues and 1 PR as blockers, of which the PR and several of...| blogs.perl.org
We were all present. CVE-2024-56406 is published and has been addressed by new point releases. Please upgrade or patch your perl promptly if affected. We thank Steve Hay, Andreas König and Stig Palmquist for doing the heavy lifting, as well...| Perl Steering Council
We continued with the potential release blocker issue review and finished going over all 49 issues remaining at this time, of which we identified 11 of interest. There are now still 72 pull requests to review.| blogs.perl.org
Preparations for the point release are now in full swing.| blogs.perl.org
We talked again about Perl 42. We think it may already be too late for it in this cycle, so we want to make a thorough case for it by releasing a side tarball for the end of this cycle, and if no technical blocker is found, actually do the jump to 44 in the next cycle.| blogs.perl.org