Mailing List Archive: perl v5.38.0 is coming

perl v5.38.0 is coming

perl.p5p at rjbs

Apr 7, 2023, 11:06 AM

Post #1 of 8 (236 views)

Porters,

We generally pretend that the May monthly release of Perl will be the new stable release. (I mostly date this to v5.14, which was released on what Americans would call 5/14.) We don't always hit it, but it's roughly the goal. That means it's time to start preparation.

Part of this is simple stuff that I'll just get to work on, like a perldelta branch that merges the v5.37.0-11 deltas.

Part of this is "deal with issues labeled Release-Blocker <https://github.com/Perl/perl5/issues?q=is%3Aopen+is%3Aissue+label%3A%22Release+Blocker%22>." Low and behold, *there are currently zero release blockers*. Sounds nice, but is it true? Sing out if you think not. But first, read this third paragraph:

Part of this is going to be "decide what we do with the question of warnings on smartmatch and the old package separator." I will post a separate thread about that issue. My take is "I really hope we can still ship those changes, but we may revert, and the question (to me) is not about *whether* we see CPAN 'no warnings' tests fail, but *which* ones." Expect to see that email sometime today.

Meantime: Blockers?

--
rjbs

Re: perl v5.38.0 is coming [ In reply to ]

perl.p5p at rjbs

Apr 8, 2023, 7:40 AM

Post #2 of 8 (236 views)

On Fri, Apr 7, 2023, at 14:06, Ricardo Signes wrote:
> Meantime: Blockers?

It had either slipped my mind or never quite entered it that BBC issues are now mostly found *not* on this list, but in GitHub.

There are three pages of them at the moment: https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC

Those will want a review, too, and I'll get to lookin' soon.

--
rjbs

Re: perl v5.38.0 is coming [ In reply to ]

jkeenan at pobox

Apr 8, 2023, 9:19 AM

Post #3 of 8 (236 views)

On 4/8/23 10:40, Ricardo Signes wrote:
> On Fri, Apr 7, 2023, at 14:06, Ricardo Signes wrote:
>> Meantime: Blockers?
>
> It had either slipped my mind or never quite entered it that BBC issues
> are now mostly found /not/ on this list, but in GitHub.
>
> There are three pages of them at the moment:
> https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC
> <https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC>
>
> Those will want a review, too, and I'll get to lookin' soon.
>

Some of those are from the 5.35 dev cycle. I was looking yesterday but
unfortunately couldn't find any way to *accurately* say, "Give me BBC
tickets that are still open and were opened after 2023-05-26." (The
results using '+opened:>YYYY-MM-DD' were visibly incorrect.)

jimk

Re: perl v5.38.0 is coming [ In reply to ]

p5p.list at perl-services

Apr 9, 2023, 2:08 AM

Post #4 of 8 (236 views)

Am 08.04.23 um 18:19 schrieb James E Keenan:
> On 4/8/23 10:40, Ricardo Signes wrote:
>> On Fri, Apr 7, 2023, at 14:06, Ricardo Signes wrote:
>>> Meantime: Blockers?
>>
>> It had either slipped my mind or never quite entered it that BBC
>> issues are now mostly found /not/ on this list, but in GitHub.
>>
>> There are three pages of them at the moment:
>> https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC
>> <https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC>
>>
>>
>> Those will want a review, too, and I'll get to lookin' soon.
>>
>
> Some of those are from the 5.35 dev cycle. I was looking yesterday
> but unfortunately couldn't find any way to *accurately* say, "Give me
> BBC tickets that are still open and were opened after 2023-05-26."
> (The results using '+opened:>YYYY-MM-DD' were visibly incorrect.)
>
> jimk
>
Try
https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+label%3ABBC+created%3A2022-05-26..2023-05-31
. That seems to be what you want...

- Renée

Re: perl v5.38.0 is coming [ In reply to ]

craig.a.berry at gmail

Apr 9, 2023, 6:59 PM

Post #5 of 8 (236 views)

On Fri, Apr 7, 2023 at 1:06?PM Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote:
> We generally pretend that the May monthly release of Perl will be the new stable release.
. . .
> Meantime: Blockers?

The following two PRs prevent two sources of blead build failure on
VMS and the second one is probably also needed for nmake builds on
Windows, though I haven't had a chance to verify that:

https://github.com/Perl/perl5/pull/21007

https://github.com/Perl/perl5/pull/21008

I have not merged these myself since I assume we are pretty deeply
frozen at this point and I could not find the current rules indicating
how and by whom commits get done during code freeze. If someone
sounding authoritative tells me what to do I'll do it :-).

Re: perl v5.38.0 is coming [ In reply to ]

sisyphus359 at gmail

Apr 9, 2023, 7:28 PM

Post #6 of 8 (236 views)

On Mon, Apr 10, 2023 at 12:00?PM Craig A. Berry <craig.a.berry@gmail.com>
wrote:

>
> The following two PRs prevent two sources of blead build failure on
> VMS and the second one is probably also needed for nmake builds on
> Windows, though I haven't had a chance to verify that:
>
> https://github.com/Perl/perl5/pull/21007
>
> https://github.com/Perl/perl5/pull/21008
>
>
I don't think nmake is affected by the second.
For the last 10 months, I've regularly been building perl devel releases
as they've become available (up to and including 5.37.10) using MSVC-143
(VS 2022) and nmake, without issue.
I do both 32-bit and 64-bit builds.

So, unless I've somehow evaded the troublesome perl source, I would say
that nmake handles things just fine as it stands.

Cheers,
Rob

Re: perl v5.38.0 is coming [ In reply to ]

craig.a.berry at gmail

Apr 9, 2023, 7:41 PM

Post #7 of 8 (236 views)

On Sun, Apr 9, 2023 at 9:29?PM sisyphus <sisyphus359@gmail.com> wrote:
>
>
>
> On Mon, Apr 10, 2023 at 12:00?PM Craig A. Berry <craig.a.berry@gmail.com> wrote:
>>
>>
>> The following two PRs prevent two sources of blead build failure on
>> VMS and the second one is probably also needed for nmake builds on
>> Windows, though I haven't had a chance to verify that:
>>
>> https://github.com/Perl/perl5/pull/21007
>>
>> https://github.com/Perl/perl5/pull/21008
>>
>
> I don't think nmake is affected by the second.
> For the last 10 months, I've regularly been building perl devel releases as they've become available (up to and including 5.37.10) using MSVC-143 (VS 2022) and nmake, without issue.
> I do both 32-bit and 64-bit builds.
>
> So, unless I've somehow evaded the troublesome perl source, I would say that nmake handles things just fine as it stands.

Good to know. I thought I saw comments somewhere indicating that
.PHONY is not supported by nmake, but maybe it is or gets suppressed
some other way.

Re: perl v5.38.0 is coming [ In reply to ]

tony at develop-help

Apr 9, 2023, 7:56 PM

Post #8 of 8 (236 views)

On Mon, Apr 10, 2023 at 12:28:57PM +1000, sisyphus wrote:
> On Mon, Apr 10, 2023 at 12:00?PM Craig A. Berry <craig.a.berry@gmail.com>
> wrote:
>
> >
> > The following two PRs prevent two sources of blead build failure on
> > VMS and the second one is probably also needed for nmake builds on
> > Windows, though I haven't had a chance to verify that:
> >
> > https://github.com/Perl/perl5/pull/21007
> >
> > https://github.com/Perl/perl5/pull/21008
> >
> >
> I don't think nmake is affected by the second.
> For the last 10 months, I've regularly been building perl devel releases
> as they've become available (up to and including 5.37.10) using MSVC-143
> (VS 2022) and nmake, without issue.
> I do both 32-bit and 64-bit builds.
>
> So, unless I've somehow evaded the troublesome perl source, I would say
> that nmake handles things just fine as it stands.

nmake appears to just treat the .PHONY directive as a target, ie. you
can do C<nmake .PHONY> to build everything listed after the ".PHONY:".

Tony