Front page | perl.perl5.porters |
Postings from December 2017
Avar wrote: > On Sat, Dec 30 2017, Tomasz Konojacki jotted: > > I'm pretty sure we will never retroactively mark feature as > > experimental ever again. > > What'll that mean? That per perlpolicy.pod we'll mark it directly as > deprecated? And thus give users even fewer releases to notice that they > shouldn't be using them? You seem to be assuming that experimental status is somehow a path to deprecation. Where are you getting that idea? If some feature is experimental, that means we are still trying it out to see if the idea works, is feasible, etc. To take an existing feature, such as dump(), and mark it now as 'experimental' in preparation for deprecation and removal makes no sense. We're effectively saying, 'oh, the feature we added 30 years ago we are now still playing with to see if it will work.' And then, 'we consider it a failed experiment.' > How's that better for our users? You're just saying that they should be > given less notice of invasive changes. If two cycles are deemed too short for a particular deprecation, there is no reason we cannot remove the feature after 3 or 4 cycles just to give people some time.Thread Previous | Thread Next