[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-porters
Subject:    Re: Update Cpan Module for Perl 5.36.0
From:       Pierrick Bouvier <pierrick.bouvier () linaro ! org>
Date:       2022-05-12 7:50:22
Message-ID: 90b4decd-d0d6-f2ad-72d8-3af16fa18717 () linaro ! org
[Download RAW message or body]

After investigation, other failures were not reproducible. I didn't 
update PR at this time. Sorry, I should have.

As a proof, I added information on PR [2], that links to our CI that ran 
those tests this morning on windows arm64 machine.

[2] - https://github.com/Perl/perl5/pull/19556#issuecomment-1124586208

On 5/12/22 01:31, Tomasz Konojacki wrote:
> On Wed, 11 May 2022 07:22:11 -0400
> James E Keenan <jkeenan@pobox.com> wrote:
> 
> 
> > The procedure we use for modules which are maintained upstream on CPAN -- a \
> > category into which Win32 falls -- is that a Perl 5 committer runs a program, \
> > Porting/sync-with-cpan, which is part of the core distribution.  This gets a \
> > tarball of the module from CPAN and merges it into the core distribution, updates \
> > metafiles, etc. 
> > Right now we are in code freeze pending the release of perl-5.36.0, tentatively \
> > targeted for May 20.  Generally speaking, we do not incorporate updated versions \
> > of CPAN distributions into core at such a late point in our production cycle.  \
> > Merging Win32-0.59 will be at the discretion of the production release manager, \
> > who I am cc-ing on this response.
> 
> Considering that apparently Win32 isn't the only failing module on
> Windows on ARM (according to [1]), I don't think it's high priority.
> 
> [1] - https://github.com/Perl/perl5/pull/19556


[prev in list] [next in list] [prev in thread] [next in thread]