2016. jan. 10. 12:57 ezt írta ("Marco Pivetta" ):
>
> 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
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 wrote:
> While I'd love to see mcrypt die, unless we all forgot ho
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
On Thu, Jan 7, 2016 at 1:32 PM, Lior Kaplan wrote:
> On Jan 7, 2016 6:59 PM, "Remi Collet" wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Le 07/01/2016 17:54, Scott Arciszewski a écrit :
>> > All,
>> >
>> > I propose the following timeline to give ext/mcrypt the viking
>> > f
On Jan 7, 2016 6:59 PM, "Remi Collet" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 07/01/2016 17:54, Scott Arciszewski a écrit :
> > All,
> >
> > I propose the following timeline to give ext/mcrypt the viking
> > funeral it deserves:
> >
> > PHP 7.1 - all mcrypt functions rais
