All,
I ended up leaving the vote open for a couple of extra days (been a
busy week), but I've now closed the ext/mysql deprecation vote. The
full results are at https://wiki.php.net/rfc/mysql_deprecation — the
short version is that the final vote was 25-12 in favour of
deprecation in PHP 5.5.
This made the second question moot, but for the record, the result
there was 26-12 in favour of option (a) (deprecation in PHP 5.6 if not
in PHP 5.5).
I'd like to apologise for not updating the RFC sooner to attempt to
capture the new arguments made on Internals against deprecation — I've
made an attempt at doing so (without getting deeply into the back and
forth that took place) now that I've had a bit of time, but if anyone
feels misrepresented or would like to detail their argument for
posterity better, please feel free to edit the RFC.
I intend to commit the patch along with the relevant test updates in
the next few days. Admittedly, I'm bad with timeframes, so please
don't hang me if it slips a little. It'll be in before beta 1, I
promise.
Thanks to everyone who participated in the discussion, and
particularly to those who voted. And particularly particularly to Ulf
for going well above and beyond in writing a monster blog post on the
matter (and for his correspondence and help off-list).
Cheers,
Adam, who is serious about that whole beer offer in an earlier e-mail,
no matter how you voted.
All,
I ended up leaving the vote open for a couple of extra days (been a
busy week), but I've now closed the ext/mysql deprecation vote. The
full results are at https://wiki.php.net/rfc/mysql_deprecation — the
short version is that the final vote was 25-12 in favour of
deprecation in PHP 5.5.This made the second question moot, but for the record, the result
there was 26-12 in favour of option (a) (deprecation in PHP 5.6 if not
in PHP 5.5).I'd like to apologise for not updating the RFC sooner to attempt to
capture the new arguments made on Internals against deprecation — I've
made an attempt at doing so (without getting deeply into the back and
forth that took place) now that I've had a bit of time, but if anyone
feels misrepresented or would like to detail their argument for
posterity better, please feel free to edit the RFC.I intend to commit the patch along with the relevant test updates in
the next few days. Admittedly, I'm bad with timeframes, so please
don't hang me if it slips a little. It'll be in before beta 1, I
promise.Thanks to everyone who participated in the discussion, and
particularly to those who voted. And particularly particularly to Ulf
for going well above and beyond in writing a monster blog post on the
matter (and for his correspondence and help off-list).Cheers,
Adam, who is serious about that whole beer offer in an earlier e-mail,
no matter how you voted.--
Considering the complexity and widely divergent views on this subject, I
think your handling of this RFC was quite exemplary. This was a very big
decision and you assumed a leadership role in getting it addressed. I
don't think any apologies are necessary in this instance. =)
--Kris
It looks like Dejan Marjanovic has added the deprecation notice to all
MySQL functions in the docs in the online editor. (Look under patches
for review. I get 0 in the total but his are there). Someone would
need to verify that he did it correctly. I don't know what 'correct'
is in this instance or I would have done this myself.