On Wed, Mar 01, 2023 at 02:11:42PM +0000, Dave Mitchell wrote: > On Mon, Feb 27, 2023 at 11:17:02AM +0100, demerphq wrote: > > But that isn't correct. Odds are *very* likely we get CPAN breakage from > > the very moment we deprecate something > > +1 > > I'm particularly troubled that we have added two major deprecations > very late in this release cycle: > > 5.37.9: deprecate Foo'Bar > 5.37.10: (not even released yet): change 'experimental' to 'deprecated': > ~~, given, when, etc. > > There seems to have been a lot of CPAN test suite breakage from these. > Even if the fixes turn out to be trivial, and even if p5p volunteer to do > all the fixing, it doesn't leave a lot of time to get new releases out and > settled in. > > So I think that > a) such deprecations in future should only come early in the blead release > cycle; > b) we should seriously consider backing out for now the two specific > Foo'Bar and ~~ deprecations and re-adding them for 5.38.1. Well, a month has passed, and in the last week or so we've had 9 new BBCs related to the new smartmatch/when deprecation. Are we agreed or not that the Foo'Bar and smartmatch deprecations should be rolled back now, and re-applied in 5.39.1? And if so, is anyone volunteering? -- Never work with children, animals, or actors.Thread Previous | Thread Next