hi Zeev, On Tue, Oct 14, 2014 at 10:08 AM, Zeev Suraski <z...@zend.com> wrote: > All, > > > > We’ve had some discussions about it during the version name & phpng RFC > processes, and now that 5.6.0 is behind us – I think it’s time to get a > more concrete game plan for PHP 7.0. > > > > I drafted an RFC that proposes a one year timeline for PHP 7.0. I believe > it strikes a good balance between early delivery to stay competitive, and > having enough time to shape a major version. Given that we’ve already made > some very substantial progress towards 7.0 (with phpng, AST, uniform > variable syntax, etc.) – I think that timeline is very realistic, and > perhaps we can even beat it. Restating the obvious, new features that > don’t have compatibility implications can always be delivered in minor > versions, i.e. 7.1, 7.2, etc. > > > > The RFC is at https://wiki.php.net/rfc/php7timeline - comments welcome!
So I have to say (again) that one year is too short. We discussed 1.5 year as a good realistic timeline and that's what I am going to propose using a competitve RFC today, unless you are willing to add the options to this RFC (would be easier). The need of a 5.7 release is also something we need to decide. I am not saying we cannot make it in less than 1.5 year, but one year, given the current status, is not realistic. Given that the engine is still a moving target, it is not realistic, fair nor correct to ask other developers to get their stuff done by 2015/1 or 2015/2, it is simply not the way I see cooperation and support for other php.net developers. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
