On 12 December 2014 at 10:07, Levi Morrison <le...@php.net> wrote: > Just because we are releasing PHP 7.0 next year (well, according to > our timeline anyway) that doesn't mean we can't release a 5.7.
Agreed. I have to apologise here — I've had a draft RFC half-written for over a week at this point that would lay out a timeline and scope for PHP 5.7 (and think I mentioned it on IRC, so I'm sorry if I forestalled someone else doing the same), and haven't had time to finish it and send it due to travelling. > The advantage of PHP 5.7 is clear to me at least: it would extend > support for the 5.X series by another year, get bug fixes, and contain > E_DEPRECATED warnings and other things that should make migrating to > PHP 7.0 easier. I personally do not suggest adding any features in PHP > 5.7. I completely agree: 5.7 should happen, and should include deprecation warnings where appropriate, reserve any keywords that will be reserved in PHP 7, and generally make it easier to maintain code that works on both versions. In terms of timeline: I think we could (and should) release this in August, assuming we stick to the limited scope above. We could really branch any time from PHP-5.6. We'll know what new warnings need to be in 5.7 by mid-March, per the PHP 7 timeline, and could then start the alpha/beta cycle there: in general, less testing should be required than normal compared to the last few versions due to the scope, and 4-5 months would be plenty to get through testing, even given that most people would be (understandably) focused on PHP 7. Adam -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
