Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79844
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <CABBJUpeWR6wZDgE3tXfMFoUGqABAftFo4unBiDYwTuh=zVwy5A@mail.gmail.com>
References: <CAF+90c-B74M82xOkT1VguqShE3b2W2YLJ1HX_XzCJtG_WUSxxg@mail.gmail.com> <CAF+90c-RGfNztweRMUxaT23xEX_Dp0YD5hvN36gXyU1dYUaVEA@mail.gmail.com> <CABBJUpeY2A3tQXm-fWXEE=c28xuBGGCA+dhKP-yhO27Y7vaurg@mail.gmail.com> <A705C44F-9AF0-4253-8A85-645835C14AEF@ajf.me> <CABBJUpeWR6wZDgE3tXfMFoUGqABAftFo4unBiDYwTuh=zVwy5A@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Sun, 21 Dec 2014 12:29:07 +0000
To: PHP internals <internals@lists.php.net>
Message-ID: <CA588609-9953-4134-954F-EF6C8E1D180B@gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] Remove deprecated functionality in PHP 7
From: rowan.collins@gmail.com (Rowan Collins)

On 21 December 2014 03:29:54 GMT, Xinchen Hui <laruence@php.net> wrote:
>Hey:
>
>
>
>On Sun, Dec 21, 2014 at 11:25 AM, Andrea Faulds <ajf@ajf.me> wrote:
>> Hey Xinchen,
>>
>>> On 21 Dec 2014, at 03:22, Xinchen Hui <laruence@php.net> wrote:
>>
>>> I am strongly against to remove ext/mysql
>>>
>>> that means, all wordpress users/maintainers,  will not able to
>upgrade
>>> to PHP7 without pain.
>>
>> It’d be in PECL and I’m sure every distro would package it, so
>there’d be no pain.
>>
>> But I also somewhat disagree with removing it, as if it’s in PECL
>having deprecation notices makes no sense, and we might get rid of
>them. :(
>>
>actually,  I hope, only hope.
>
>we release PHP7 without any big BC break, give people transparent
>performance improvement..
>
>then we can do minor bc breaks in the second number releases... 7.1 ,
>7.2

That is more or less the opposite of the agreed release process - obviously we can have *minor* bc breaks later, but putting things off from a 7.0 release to encourage adoption just puts off the problem and risks 7.1 becoming a repeat of 5.3/5.4 in terms of adoption.