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

Deprecation doesn't mean we have two release cycles before thingsbreak.

Thread Next
February 27, 2023 10:17
Deprecation doesn't mean we have two release cycles before thingsbreak.
Message ID:
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. But that
isn't correct. Odds are *very* likely we get CPAN breakage from the very
moment we deprecate something, as many modules test to see if they generate
warnings when they run. This can be transitive breakage with "action at a
distance", where distribution A uses B uses C used D which uses a
deprecated feature, and only A actually fails test because it tests for
warnings but B and C and D do not.

So it is important we understand that deprecating something does NOT give
us two years to fix CPAN, instead it typically means we will have breakage
from the next release that contains the deprecation. We have breakage from
smartmatch and from apostrophe as a package separator already and i expect
over the coming weeks we will get reports about quite a bit more.

It would be nice if people in the community would help out with this and
contribute patches and bug reports, etc, for these issues and take on some
of the "blead breaks CPAN" burden of these changes.


perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About