For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to:
https://www.mediawiki.org/wiki/PHP_5.4
To be honest, the upgrade isn't that exciting. The only real worthwhile new feature is traits. Everything else is just random fixes in syntax. As for the timetable for this, PHP 5.3 isn't going anywhere anytime soon, so there's no way we can stop supporting it.
What I'm really excited about is PHP 5.5, which has generators, finally clauses, dereferencing of container literals, and a new password hashing API. Unfortunately it'll be literally a decade before we switch to that. :(
*-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerromeo@gmail.com
On Sun, Jun 9, 2013 at 7:18 AM, Daniel Friesen daniel@nadir-seen-fire.comwrote:
For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to:
https://www.mediawiki.org/**wiki/PHP_5.4https://www.mediawiki.org/wiki/PHP_5.4
-- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
______________________________**_________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l
Am 09.06.2013 19:49, schrieb Tyler Romeo:
What I'm really excited about is PHP 5.5, which has generators, finally clauses, dereferencing of container literals, and a new password hashing API....
and let me add: ..... the integrated ZEND opcode cache in 5.5 see https://github.com/php/php-src/blob/php-5.5.0RC3/NEWS
9 Июнь 2013 г. 21:51:13 пользователь Tyler Romeo (tylerromeo@gmail.com) написал:
To be honest, the upgrade isn't that exciting. The only real worthwhile new feature is traits. Everything else is just random fixes in syntax. As for the timetable for this, PHP 5.3 isn't going anywhere anytime soon, so there's no way we can stop supporting it. What I'm really excited about is PHP 5.5, which has generators, finally clauses, dereferencing of container literals, and a new password hashing API. Unfortunately it'll be literally a decade before we switch to that. :( *-- *
It will probably happen much faster. PHP 5.4 is a kind of experimental branch, for example there is no stable APC opcode cache for that version. Dmitriy
Hey,
An interesting question to ask here is why the WMF is still running PHP 5.3, and what the plans are for upgrading to 5.4.
In general MW seems to work just fine on PHP 5.4 or 5.5. One possible exception being that update.php appears to have been broken with PHP 5.5 yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=49819
Cheers
-- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 --
On Wed, 19 Jun 2013 07:22:14 -0700, Jeroen De Dauw jeroendedauw@gmail.com wrote:
Hey,
An interesting question to ask here is why the WMF is still running PHP 5.3, and what the plans are for upgrading to 5.4.
In general MW seems to work just fine on PHP 5.4 or 5.5. One possible exception being that update.php appears to have been broken with PHP 5.5 yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=49819
Cheers
-- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 --
Presumably they're still using PHP 5.3 because Precise (12.04 LTS) is still on PHP 5.3: http://packages.ubuntu.com/precise/php5
Only the non-LTS releases have PHP 5.4.
...that said, I hope we don't have to wait till April 2017 when that LTS goes EOL before we can kill PHP 5.3.
On Wed, Jun 19, 2013 at 11:03 AM, Daniel Friesen daniel@nadir-seen-fire.com wrote:
Presumably they're still using PHP 5.3 because Precise (12.04 LTS) is still on PHP 5.3: http://packages.ubuntu.com/precise/php5
Only the non-LTS releases have PHP 5.4.
...that said, I hope we don't have to wait till April 2017 when that LTS goes EOL before we can kill PHP 5.3.
I doubt it. I imagine we'll look to the new LTS when it comes out.
-Chad
On 06/19/2013 11:35 AM, Chad wrote:
I doubt it. I imagine we'll look to the new LTS when it comes out.
In the meantime, for an entirely different reason, I'm currently working on a backport of Apache 2.4 onto precise, and that includes having to rebuild PHP. Right now, the build defaults to 5.5 but I was planning on building 5.3 against it instead so that it tracked WMF production.
It would probably be /easier/ for me to build 5.4 or 5.5 alongside it instead if we want to play with Apache 2.4/PHP 5.4 with an eye towards production.
-- Marc
Le 21/06/13 00:09, Marc A. Pelletier a écrit :
In the meantime, for an entirely different reason, I'm currently working on a backport of Apache 2.4 onto precise, and that includes having to rebuild PHP. Right now, the build defaults to 5.5 but I was planning on building 5.3 against it instead so that it tracked WMF production.
It would probably be /easier/ for me to build 5.4 or 5.5 alongside it instead if we want to play with Apache 2.4/PHP 5.4 with an eye towards production.
If you want a playground, we could get both backported packages on the beta cluster (labs project: deployment-prep). That might help catch some potential issues.
I have no idea how we could get different versions in production and labs, but I am sure someone know :-D
Le 21/06/13 21:03, Antoine Musso a écrit:
If you want a playground, we could get both backported packages on the beta cluster (labs project: deployment-prep). That might help catch some potential issues.
I have no idea how we could get different versions in production and labs, but I am sure someone know :-D
Just the same way you could be using debian stable plus a few packets from debian testing. It's dpkg
Le 22/06/13 00:58, Platonides a écrit :
Le 21/06/13 21:03, Antoine Musso a écrit:
If you want a playground, we could get both backported packages on the beta cluster (labs project: deployment-prep). That might help catch some potential issues.
I have no idea how we could get different versions in production and labs, but I am sure someone know :-D
Just the same way you could be using debian stable plus a few packets from debian testing. It's dpkg
I was merely wondering how to do that in puppet where we will want 5.3 on production and 5.4 on the beta cluster.
On 22 June 2013 00:58, Platonides Platonides@gmail.com wrote:
Just the same way you could be using debian stable plus a few packets from debian testing. It's dpkg
Another option is to have multiple repositories (say: stable and testing) in your sources.list, and using pinning: https://help.ubuntu.com/community/PinningHowto
Le 09/06/13 13:18, Daniel Friesen a écrit :
For those of you wishfully waiting for the day we can require PHP 5.4 to use MediaWiki feel free to add your wishes to:
Thank you for that document. To me the only worthwhile feature is traits which would make some part of the code a bit cleaner or easier to organize.
I like the short array syntax, but I do not think it is worth breaking PHP 5.3 compatibility just to save a few keystrokes :-)
PHP 5.4 also brings some performances boosts (I have no metrics though). But nothing seems to our 5.3 codebase to run on 5.4, so there is no hurry to upgrade our requirement.
Closure changes and traits would indeed be really nice.
Short array syntax is a plus too.
-- View this message in context: http://wikimedia.7.x6.nabble.com/PHP-5-4-we-wish-tp5006788p5006809.html Sent from the Wikipedia Developers mailing list archive at Nabble.com.
PHP 5.4 does seem to be able to cause some trouble, see for example https://gerrit.wikimedia.org/r/#/c/69807/ .
We should have stayed on PHP4 if this is a trouble. Perfomance may be a problem (which is not much in 5.4 iirc), syntax flaws may be a problem (and this one fixes one of the flaws). Yes, it will take us some time to upgrade MW to 5.4 or 5.5, but deprecations are detected by any contemporary PHP IDE, and it is a matter of minutes to fix them.
On Fri, Jun 21, 2013 at 1:22 AM, Bartosz Dziewoński matma.rex@gmail.comwrote:
PHP 5.4 does seem to be able to cause some trouble, see for example https://gerrit.wikimedia.org/**r/#/c/69807/https://gerrit.wikimedia.org/r/#/c/69807/.
-- Matma Rex
______________________________**_________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-lhttps://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Fri, 21 Jun 2013 12:32:02 +0200, Paul Selitskas p.selitskas@gmail.com wrote:
We should have stayed on PHP4 if this is a trouble. Perfomance may be a problem (which is not much in 5.4 iirc), syntax flaws may be a problem (and this one fixes one of the flaws). Yes, it will take us some time to upgrade MW to 5.4 or 5.5, but deprecations are detected by any contemporary PHP IDE, and it is a matter of minutes to fix them.
Sure, these are just bugs that need fixing. Someone has to go through the codebase and fix them, though.
On Fri, 2013-06-21 at 13:35 +0200, Bartosz Dziewoński wrote:
Sure, these are just bugs that need fixing. Someone has to go through the codebase and fix them, though.
There are also a few bugs with the "newphp" keyword: https://bugzilla.wikimedia.org/buglist.cgi?keywords=newphp&keywords_type...
andre
On 21/06/13 12:32, Paul Selitskas wrote:
We should have stayed on PHP4 if this is a trouble. Perfomance may be a problem (which is not much in 5.4 iirc), syntax flaws may be a problem (and this one fixes one of the flaws). Yes, it will take us some time to upgrade MW to 5.4 or 5.5, but deprecations are detected by any contemporary PHP IDE, and it is a matter of minutes to fix them.
I have been running 5.4 for a long time without problems. The only relevan difference I can think is the difference on mb_check_encoding(), restricted to newer (smaller) unicode range, which then causes a difference on StringUtils::isUtf8. We can change our php implementation and StringUtilsTest to match that, but then those 5 tests will fail on PHP 5.3.
See bug 43679 - https://bugzilla.wikimedia.org/43679
wikitech-l@lists.wikimedia.org