Upcoming 5.34.1 release

Front page | perl.perl5.porters | Postings from February 2022

Thread Next

From:

Steve Hay via perl5-porters

Date:

February 20, 2022 17:38

Subject:

Upcoming 5.34.1 release

Message ID:

CADED=K48M52rK=sgCfbNBNOdHUkZBUqV7QR7rPM7LiJe1Tm9oQ@mail.gmail.com

Apologies for this being a few months later than I intended, but I
have finally got round to producing a voting file for proposals to get
into 5.34.1, which I would like to release soon (i.e. well before
5.36.0).

It must be said that nothing urgent requiring an earlier 5.34.1
release has occurred, otherwise I would have been on it much sooner.
Indeed, the GitHub 5.34.1 milestone
(https://github.com/Perl/perl5/milestone/15) never had any issues
added to it, and the backport-5.34 label
(https://github.com/perl/Perl5/issues?q=+label%3Abackport-5.34) only
had 4 things in it, two of which don't really meet the backporting
criteria set out in perlpolicy anyway. (I've added those two to the
bottom of the voting file, in the "Others" section.)

The list is available in the usual place:

https://perl5.git.perl.org/perl5.git/blob/refs/heads/maint-votes:/votes-5.34.xml

(The raw file (https://perl5.git.perl.org/perl5.git/blob_plain/refs/heads/maint-votes:/votes-5.34.xml)
views nicely rendered in some web browsers, e.g. Firefox.)

I've tested all these changes. Two require some VERSION bump magic,
and a963d6d5acabdd8c78afec507b56f890de6d346a has some whitespace
conflicts because of 1f4fbd3b4b26604673abca2a5f911744e826b1f3, but
otherwise they're all good as far as applying and testing are
concerned.

Please shout if you think anything else that fits the perlpolicy
backporting criteria is worthy of being included.

Committers: Please have a look and consider adding your votes.

Note that there were numerous other changes that I encountered on my
trawl through history since 5.34.0 which might be nice to include, but
again don't really meet the current backporting criteria:

8f432bc3ba fix utime() to set $!/errno when called on a closed handle
73a0855d2e PathTools: compare inode numbers as strings
76d2194af3 File::Copy: compare inode numbers as strings

f72873660d gh18842: fix a pair of sprintf format warnings

499aa13271 gh18770: stop scanning for substrs after *COMMIT

57a643a6b0 mktables: Fix debugging issues

5892d8f56e gh19081: also deliver SIGFPE in an "unsafe" manner

2536d892ff A test for the order of untie/iterator state interaction
71e2181fdc Free tied hash iterator state immediately at the `untie` call

999b4e2f82 Fix function calls being misinterpreted as bareword
filehandles [GH #19271]
5f5ca502c6 Also fix paren-less calls of subs where a filehandle could be

Steve

Thread Next