Re: mcrypt extermination plan

Edit: never mind - I must have misread somewhere that dropping in 7.2 was a plan. Sorry for the misunderstanding! Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 10 January 2016 at 12:56, Marco Pivetta <ocramius@gmail.com> wrote: > While I'd love to see mcrypt die, unless we all forgot how semver works, > this isn't how it can be done :-\ > If you want to actually drop something, regardless of how bad it is (and I > know mcrypt is bad), then the next major version is where this should > happen. > Note that pushing for an earlier 8.0 is not a problem either. > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > On 7 January 2016 at 20:12, Pierre Joye <pierre.php@gmail.com> wrote: > >> On Jan 7, 2016 11:54 PM, "Scott Arciszewski" <scott@paragonie.com> wrote: >> > >> > All, >> > >> > I propose the following timeline to give ext/mcrypt the viking funeral >> > it deserves: >> > >> > PHP 7.1 - all mcrypt functions raise E_DEPRECATED >> > PHP 8.0 - remove ext/mcrypt, only make it available through PECL >> > >> > There will be no compatibility layer in this proposal, but if someone >> > wants to build one that sits atop openssl, feel free to do that >> > separately. >> > >> >> Sounds good to me :) >> > >