On 11/20/2016 02:32 PM, Rowan Collins wrote:
I'm not sure what you mean by "political". The big challenge which comes
up again and again, is that take up of new versions of PHP is low. You
can blame the users for that if you like, but the reality is there's no
point rushing your shiny feature into a release that 90% of the user
base won't install.
For the perspective of a user on this -
I always skip a major version. I'm running 5.6.x on my productions, and
preparing for 7.1 I am running 7.1.0RC on one test server and my
workstation. I'll probably run 7.1 on production fairly soon after
release but likely skip 7.2.
I skip because once I have a web application deployed, I'm not looking
to change it for awhile, security updates sure but I don't need to run
the latest major release when the release I have works fine.
I suspect many are the same way, and I don't see that as a bad thing.
Releases no longer maintained by upstream obviously should not be run,
but if the release one has works for the purpose, what problem is solved
by upgrading to latest major release? It's time consuming and expensive
because there is always code that needs to be changed and tested.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
