Front page | perl.perl5.porters |
Postings from February 2022
We discussed perldelta naming at the last PSC meeting, and agreed that there’s too much benefit to having the file called perldelta.pod in blead, specifically so people can be told "if you make a change of note, update perldelta.pod", rather than having to put [version].[revision] in there. And it’s somewhat handy that I can type `perldoc perldelta` to find the changes in my locally installed version of Perl. Dan wrote: > One thing that could be changed without breaking this is to have the perldelta copied to its new version during the RMG distribution process, rather than on installation - this would fix its availability on metacpan, as discussed in https://github.com/metacpan/metacpan-web/issues/2587 and related issues. The key word here presumably being *copied*? So when 5.35.9 is released, it would have both perldelta.pod and perldelta5359delta.pod, with identical contents, and the RMG would still have the post-release action to create a new perldelta.pod in blead. This feels like a good step. NeilThread Next