On 20 Jul 2015, at 22:42, Legoktm
<legoktm.wikipedia(a)gmail.com> wrote:
OTOH, if we never bump our version requirements, there's less incentive
for hosting providers to upgrade their PHP. [1] has some interesting
arguments regarding this.
[1]
http://blog.ircmaxell.com/2014/12/on-php-version-requirements.html
Indeed. Providers that don't already provide newer PHP options, will certainly
start doing so when major software requires it.
On 21 Jul 2015, at 07:12, bawolff
<bawolff+wn(a)gmail.com> wrote:
https://wikiapiary.com/w/index.php?title=Special:SearchByProperty&limit…
is also something to keep in mind
Yes, but also keep in mind that many of those wikis likely run in hosting
environments that already support newer PHP versions. But customers won't
change their settings until they have to. And providers can't change
customers proactively without risking site breakage or damaging customer
relations.
I had the same with my third-party wikis. Until recently they ran on PHP
5.3. Then at some point I realised my provider had a simple "Select PHP
Version" page in the control panel. I switched them all to PHP 5.6 that day
and also enabled opcache. Site performance improved greatly.
On 19 Jul 2015, at 07:15, Bryan Davis
<bd808(a)wikimedia.org> wrote:
Some WMF production hosts are still on PHP 5.3.10 so as Tim pointed
out last spring [0] we shouldn't drop 5.3 support until after the
entirety of the WMF server fleet are all switched over to HHVM or at
least a newer version of PHP5. [..]
[0]:
http://www.gossamer-threads.com/lists/wiki/wikitech/436441#436441
Yeah, in case of Wikimedia master is near-immediate production so
let's post-pone this until right after Wikimedia's migration is complete.
Third parties can stick to using the LTS or the current stable version
as needed for upto several years more without issue.
-- Krinkle