Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71227
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAL0xaBGUv5vsQUO1ZLq-uYT_8goWB8pKTMukk7vnWZRwcD7R=w@mail.gmail.com>
References: <CAMUwpuSoK9BmchwCx88QXicKmwJ9AmzRkwwMqXsrpSjkukCkRg@mail.gmail.com>
	<CAL0xaBGUv5vsQUO1ZLq-uYT_8goWB8pKTMukk7vnWZRwcD7R=w@mail.gmail.com>
Date: Fri, 17 Jan 2014 20:55:38 -0500
Message-ID: <CAL+t6cFL-vtpB5b26_jDcXmC36aT9ZXpRUvNGDSi-5J4f7sRVg@mail.gmail.com>
To: Arvids Godjuks <arvids.godjuks@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04426c3a84ca3c04f034f452
Subject: Re: [PHP-DEV] 5.5 to 5.6 cleanup
From: theanomaly.is@gmail.com (Sherif Ramadan)

--f46d04426c3a84ca3c04f034f452
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 17, 2014 at 8:35 PM, Arvids Godjuks <arvids.godjuks@gmail.com>wrote:

>
> As it was mentioned, it was not decided that mysql ext should be completly
> removed at 5.6, my personal opinion is that it should be pushed po PECL at
> this release with all the bells and whistells warning everyone that
> extension is depricated and will be removed soon (read: next release - be
> it 5.7 or 6.0).


The plan was always to move ext/mysql to PECL. We've never removed an
entire extension from the source completely without it going to PECL (as in
the case of SQLite). Which is why the decision was made to first update the
documentation warning people that ext/mysql would soon be deprecated. Later
the decision was made to start issuing E_DEPRECATED errors in PHP 5.5, as
per the aforementioned RFC that was accepted. This has all been done
already. The next step is to remove ext/mysql from PHP core and place into
PECL. The various linux distributions will likely still package it
separately as they already do with other various PHP extensions. So this
will not likely affect those who rely on using their distribution's package
manager to install PHP extensions. However, that is not to say that we
should spring things upon users suddenly and without taking the necessary
steps to ensure a smoother transition.


> I belive that leaving everything as is right now will be
> sending a message that projects like Wordpress can halt the progress of the
> language development and block the decisions like removal of the mysql ext.
>
>
I agree that we should not be waiting on Wordpress to update their code in
order to make the decision of removing ext/mysql. In fact, in our previous
discussion back in 2012, Wordpress claims they were the ones waiting on us
before they updated their code http://news.php.net/php.internals/63929

We've given fair warning that the extension will be removed soon. I'm just
saying that the decisions to remove it was never finalized to 5.6. We've
ramped-up our release cycles and we've gone from 5.4 to 5.5 to 5.6 in less
than 2 years now.

--f46d04426c3a84ca3c04f034f452--