On Oct 6, 2016 3:41 PM, "Nikita Popov" <nikita....@gmail.com> wrote: > > On Thu, Oct 6, 2016 at 5:22 AM, Davey Shafik <da...@php.net> wrote: >> >> On Wed, Oct 5, 2016 at 8:11 PM, Pierre Joye <pierre....@gmail.com> wrote: >> >> > hi Leigh, >> > >> > On Tue, Oct 4, 2016 at 11:58 PM, Leigh <lei...@gmail.com> wrote: >> > > Hello list, >> > > >> > > It is my intention to create a new PECL package for ext/mcrypt, so >> > > that it can be removed from master as per the RFC >> > > (https://wiki.php.net/rfc/mcrypt-viking-funeral) >> > > >> > > I do not expect there to be any updates to the extension after it has >> > > been migrated, however we voted to move it there. >> > > >> > > Any objections/comments? If not I'll apply for my PECL account in the >> > > next few days. >> > >> > I am not sure to follow. >> > >> > We rejected to move it out of the core for 7.0. This RFC is about >> > deprecation for 7.1. >> > >> > As much as I want to kill this beast as soon as possible, I do not >> > think we can kill it in 7.x but 8.x. It is also why I was pushing so >> > hard to kill it in 7.0, knowing that this will be tried again and >> > sadly for 7.x. >> >> >> From the RFC: >> >> > In PHP 7.1+1 (be it 7.2 or 8.0), the crypt extension will be moved out of >> core and into PECL >> >> and >> >> > Vote “Yes” to raise an E_DEPRECATED notice in PHP 7.1 when any crypt >> function is used and to remove the extension from core in 7.1+1. >> >> So, per the RFC, moving to PECL in 7.2 is correct. >> >> - Davey > > > Furthermore the release process RFC *explicitly* allows moving extensions to PECL in minor versions.
I am *not* (I can emphasize text too ;) it is not allowed. What I am saying is why we refused to do it in 7.0 and then the same go all in for 7.2. That makes no sense to me and it is something we should figure out for 8 (exts or behaviors).
