Le 06/12/2015 18:36, Zeev Suraski a écrit :
The 'sin' of the PHP 4 EOL was - well - that we didn't have one for a very long time.
An important 'sin' of the PHP 4 EOL is also the massive backport of PHP 5 features during years, which didn't push people to migrate.
In general, I don't think timelines make sense to commit to before a version is released. If for whatever reason a release gets delayed it makes no sense that you'd be forced, as a user, for a shorter upgrade cycle. Something along the lines of Francois' suggestion - where the lifetime of version N-1 relates to the release date of version N is definitely needed, and that was the thinking behind the release process timeline to begin with.
Yes, starting counting from the release date of version N is better. So, instead of giving one additional year of support, what about a guarantee of 2 years of active support on <N - 1>.<last> starting from <N>.0 release date ? That would extend 5.6 active support to Dec 2017, and EOL on Dec 2018, which is a good trade-off, IMHO.
Regards François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
