Front page | perl.perl5.porters |
Postings from March 2023
On Mon, Feb 27, 2023, at 05:17, demerphq wrote: > There seems to be this idea that if we deprecate something that we have two release cycles, IOW, two *years*, before we have to get stuff fixed, and that the only code which might be broken by the deprecation is code that use fatal warnings, which we generally advise people not to use. I saw later that you said this was said on IRC, so I don't want to say that this idea doesn't exist. I believe you heard this, which means somebody said it, which means somebody probably thinks it! But on the "why is there a two year deprecation period" angle, I thought I should restate some of the reasoning behind that from discussions around when we got more formal about it: Two years means that users who reliably upgrade their perl from their package manager, and upgrade their OS distribution, are very likely to see the deprecation in new perl from their distribution before they see breakage. It's about giving people a notice period, rather than giving ourselves time to put off fixing CPAN. As Yves says, CPAN is affected on day one on the new version. -- rjbsThread Previous | Thread Next