Hi! > That means 5.6 EOL is 20 months and 11 days away. That's more than one > and a half years, it should be enough time to upgrade.
I'm not sure what you mean here by "should be". If you mean "if everybody dropped everything right now and started only working on upgrade to PHP 7 then they could make it in 20 months" - yes, it is reasonably true. But nobody would do that. In fact, in many places base version is still 5.3. Again, we can talk that people "should" do this and "should" do that until we're blue in the face, but that's not going to happen, whatever we talk about. Only one of the two things is going to happen: 1. People would run 5.x in 2017 as supported version and get the fixes. 2. People would run 5.x in 2017 as unsupported version, get no fixes and suffer from it. > However, I'm not sure if extending the release date now is the best > idea. 7.0.0 has only been out for four days. We don't know where the > ecosystem will be in August 2017 or how many people will have migrated. > At this stage, I'm not sure we can assess whether we need an extension. We don't know that about 7.0, but it's not the first version we've released. We know what happened with previous versions. So please tell me, based on that past experience - does the scenario of "majority of users are running 7.x in 2017" sound realistic? > Furthermore, postponing EOL now means reduced pressure to upgrade to 7. Again, if you think people's decision to upgrade significantly depends on that, I think you are deluding yourself. We have tons of "pressure" to upgrade from EOLed 5.x versions. We still got majority of people running them, and more sites running 5.2 than 5.6, judging by http://w3techs.com/technologies/details/pl-php/5/all -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
