>> - If we go for 5.7 : >> We could release it this summer (2015) , but that would mean that 7.0 >> wouldn't come before summer 2016. >> Releasing a 5.7 will lean the release cycle curve, but it is not >> mandatory, that >> should be debatted. > > A 5.7 that pushes 7.0 into Summer 2016 is IMHO a strategic mistake, but > regardless I think the discussion is moot. We've already decided we're > aiming for a 2015 PHP 7.0 release, and should stick to that plan.
Assuming we do a PHP 5.7 as I outlined previously, it shouldn't take anything more than a few hours here and there by a release manager and a tiny bit of extra work for a few RFC authors. It's just normal bug fixes, version bump, and compatibility stuff for PHP 7. As long as we keep features out of PHP 5.7 it should not delay a PHP 7 release. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
