develooper Front page | perl.perl5.porters | Postings from February 2023

Re: Deprecation doesn't mean we have two release cycles beforethings break.

Thread Previous | Thread Next
From:
"G.W. Haywood" via perl5-porters
Date:
February 27, 2023 12:00
Subject:
Re: Deprecation doesn't mean we have two release cycles beforethings break.
Message ID:
d93523a-3ea-fcfb-3fbd-b91bfc57c8cc@jubileegroup.co.uk
Hi there,

On Mon, 27 Feb 2023, demerphq wrote:

> On Mon, 27 Feb 2023 at 12:19, G.W. Haywood via perl5-porters wrote:
>> On Mon, 27 Feb 2023, Dave Cross wrote:
>>> On Mon, 27 Feb 2023 at 10:56, G.W. Haywood via perl5-porters wrote:
>>>
>>>>
>>>> I'm the maintainer of exactly one CPAN module, but since it's used by
>>>> both Sendmail and Postfix users I'm very keen to keep it working.  It
>>>> would help me greatly in this effort if for example a row or two could
>>>> be added to this table:
>>>>
>>>> http://matrix.cpantesters.org/?dist=Sendmail%3A%3APMilter
>>>>
>>>> to show development versions of Perl ...
>>>
>>> The top seven rows on that page already show the most recent development
>>> versions of Perl. So I'm not really sure what more information you're
>>> asking for.
>>
>> Sorry, maybe I misunderstand.
>
> I think you did. That tables lists released versions. Such tables would not
> list every patch in blead.
>
>> Is one of those what you'd call 'blead'?
>
> No.

In that case I don't I misunderstood - I think you did.  But that's
probably because I'm unfamiliar with the terminology and don't know
how to express my ideas so people on this list can understand them.

> You would need to build perl from a checkout of the repo at
> https://github.com/Perl/perl5

My point exactly.  And in my case, because of my pathological aversion
to github (and github's aversion to my browser), I simply won't do it.

> That wasn't my point however, my point was it would be helpful if folks
> could take the time to build perl against the latest commit in the blead
> branch on github and then test it against their favourite modules. If
> anything doesn't build, file a patch with the author of the module and or
> maybe with us as an issue.

That's incredibly onerous.  Can't you just get the patched version(s)
of Perl into cpan-testers and get everything tested automatically by
the next morning, together with a nice page of idiot lights which show
Where Things Failed?

-- 

73,
Ged.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About