Mailing List Archive

Congrats, saw it hours before in 4610ba610afe382010b4c68c81c72b0302d89423

https://github.com/Perl/perl5/commit/4610ba610afe382010b4c68c81c72b0302d89423

Think and hope June 30 will be the date for the actual release! ????
[https://opengraph.githubassets.com/a12ee15f1fb18567667587210314f6646d12e9b8bd460c0b5f5f50ea444bc31c/Perl/perl5/commit/4610ba610afe382010b4c68c81c72b0302d89423]<https://github.com/Perl/perl5/commit/4610ba610afe382010b4c68c81c72b0302d89423>
prepare for v5.38.0-RC2 · Perl/perl5@4610ba6<https://github.com/Perl/perl5/commit/4610ba610afe382010b4c68c81c72b0302d89423>
???? The Perl programming language. Contribute to Perl/perl5 development by creating an account on GitHub.
github.com
?

________________________________
From: Ricardo Signes <perl.p5p@rjbs.manxome.org>
Sent: Friday, June 23, 2023 11:19 PM
To: Perl 5 Porters <perl5-porters@perl.org>
Subject: perl v5.38.0-RC2 is now available

Oh, do not forsake me, my indolent friends
Oh, do not forsake me though you know I must spend
All my darkest hours talking like this
For I am one thousand years old

— They Might Be Giants, O Do Not Forsake Me

We are happy to announce the second release candidate of Perl v5.38.0.

You will soon be able to download Perl 5.38.0-RC2 from your favorite CPAN mirror or find it at:

https://metacpan.org/release/RJBS/perl-5.38.0-RC2/

SHA256 digests for this release are:

2a9f3be3ebb78463ba56d443de986145672ea0e63384b0689a908ea67c5e08c1 perl-5.38.0-RC2.tar.gz
1bb4b25a99378eea914263d6078390e90413b72711d7b9a9ccfe0c0d65559509 perl-5.38.0-RC2.tar.xz

You can find a full list of changes in the file "perldelta.pod" located in the "pod" directory inside the release and on the web at

https://metacpan.org/pod/release/RJBS/perl-5.38.0-RC2/pod/perldelta.pod

We expect to release v5.38.0 on Friday, June 30th.. Please test this release candidate and let us know of any showstoppers.

--
rjbs

On Fri, Jun 23, 2023 at 05:19:15PM -0400, Ricardo Signes wrote:
>
> You can find a full list of changes in the file "perldelta.pod" located in the "pod" directory inside the release and on the web at
>
> https://metacpan.org/pod/release/RJBS/perl-5.38.0-RC2/pod/perldelta.pod
>

Skimming that document, I noticed that versions of Perl are listed in
slightly different ways.

* https://metacpan.org/release/RJBS/perl-5.38.0-RC2/view/pod/perldelta.pod#Changes-to-%22thread-safe%22-locales
mentions "Perl 5.28" and later "v5.38"
* https://metacpan.org/release/RJBS/perl-5.38.0-RC2/view/pod/perldelta.pod#Use-of-'-as-a-package-name-separator-is-deprecated
mentions "Perl 5.42"
* https://metacpan.org/release/RJBS/perl-5.38.0-RC2/view/pod/perldelta.pod#Switch-and-Smart-Match-operator
mentions "v5.42.0"

Should we be more consistent? Is there an "official" way we want to
reference Perl versions in the documentation?

Also, some GitHub issues have links, and others don't. Some are
referenced as "GH #xxx" and others as "github #xxx".

This document is also the only one in the entire source that uses "PPC"
to mean "Perl Proposed Change" (and not "PowerPC"), but the term is
introduced nor explained nowhere in the documentation. Is it worth an
explanatory paragraph somewhere? (in the perldelta itself, or some other
place, like perlpolicy or perlhack)

--
Philippe Bruhat (BooK)

Ignorance weaves a web from which none can escape.
(Moral from Groo The Wanderer #52 (Epic))

On Tue, Jun 27, 2023 at 8:48?AM Philippe Bruhat (BooK) <book@cpan.org>
wrote:


> This document is also the only one in the entire source that uses "PPC"
> to mean "Perl Proposed Change" (and not "PowerPC"), but the term is
> introduced nor explained nowhere in the documentation. Is it worth an
> explanatory paragraph somewhere? (in the perldelta itself, or some other
> place, like perlpolicy or perlhack)
>

On a related note, it would nice to see an explanation of why we switched
from RFC (which I think everyone groks) to PPC (which not everyone does).
Was there a benefit I missed?

(Sorry. I assume this was asked and answered somewhere before)

Best,
Ovid
--
Curtis "Ovid" Poe
--
CTO, All Around the World
World-class software development and consulting
https://allaroundtheworld.fr/

Ovid wrote:
> On Tue, Jun 27, 2023 at 8:48?AM Philippe Bruhat (BooK) wrote:
>>
>> This document is also the only one in the entire source that uses "PPC"
>> to mean "Perl Proposed Change" (and not "PowerPC"), but the term is
>> introduced nor explained nowhere in the documentation. Is it worth an
>> explanatory paragraph somewhere? (in the perldelta itself, or some other
>> place, like perlpolicy or perlhack)

I'd say yes, but it doesn't seem to be particularly urgent. It could probably wait for 5.39.0. perlpolicy and perlhack seem like sensible places to explain the term.


> On a related note, it would nice to see an explanation of why we switched from RFC (which I think everyone groks) to PPC (which not everyone does). Was there a benefit I missed?

The concern was ambiguity with IETF RFCs; see also:

https://www.nntp.perl.org/group/perl.perl5.porters/2023/01/msg265548.html
https://www.nntp.perl.org/group/perl.perl5.porters/2023/03/msg265892.html


--
Arne Johannessen
<https://arne.johannessen.de/>

On Mon, Jun 26, 2023 at 11:49?PM Philippe Bruhat (BooK) <book@cpan.org>
wrote:

> Also, some GitHub issues have links, and others don't. Some are
> referenced as "GH #xxx" and others as "github #xxx".
>

FWIW the RMG has a recommended format for github references in perldelta,
namely GH #1234. If everyone follows this format, you can use the
(provided) perl-pie oneliner for turning those into pod links:

$ perl -p -i -e'BEGIN{undef $/}; s{(GH\s+#)(\d+)}{L<$1$2|
https://github.com/Perl/perl5/issues/$2>}mg' pod/perldelta.pod

On Thu, 29 Jun 2023 at 04:49, Karen Etheridge <perl@froods.org> wrote:

> On Mon, Jun 26, 2023 at 11:49?PM Philippe Bruhat (BooK) <book@cpan.org>
> wrote:
>
>> Also, some GitHub issues have links, and others don't. Some are
>> referenced as "GH #xxx" and others as "github #xxx".
>>
>
> FWIW the RMG has a recommended format for github references in perldelta,
> namely GH #1234. If everyone follows this format, you can use the
> (provided) perl-pie oneliner for turning those into pod links:
>
> $ perl -p -i -e'BEGIN{undef $/}; s{(GH\s+#)(\d+)}{L<$1$2|
> https://github.com/Perl/perl5/issues/$2>}mg' pod/perldelta.pod
>

That sounds like good motivation to preprocess pod files during release

On Fri, Jun 23, 2023 at 05:19:15PM -0400, Ricardo Signes wrote:

>
> We expect to release v5.38.0 on Friday, June 30th.. Please test this release candidate and let us know of any showstoppers.

Hi, not sure if this is a showstopper or not, but just in case:

https://rt.cpan.org/Public/Bug/Display.html?id=146411

in Math-BigInt is a regression that's fixed in 1.999838
but core currently has only 1.999837 .

% perl -Mbignum -e '1 | (1 >> 1)'
Deep recursion on subroutine "Math::BigInt::bior" at /usr/share/perl5/Math/BigFloat.pm line 3883.
Deep recursion on subroutine "Math::BigFloat::bior" at /usr/share/perl5/Math/BigInt.pm line 3513.

Sorry to be so late with this, and many thanks for your work.
--
Niko Tyni ntyni@debian.org