I think 1 year is reasonable timeline. We still have 5 month for active development and implementation of new ideas.
I think https://wiki.php.net/ideas/php6/engine is a bit outdated. I'm not sure if anyone are going to work on proposals from 2009 (even if they are great). It would be great to define an ongoing set of changes that we would definitely like to see in PHP-7.0 including the responsible person(s) and time estimation. If something can't be developed by 7.0 release, it most probably may wait for 7.1. Thanks. Dmitry. On Tue, Oct 14, 2014 at 12:46 PM, Julien Pauli <jpa...@php.net> wrote: > On Tue, Oct 14, 2014 at 10:26 AM, Xinchen Hui <larue...@php.net> wrote: > > Hey: > > > > On Tue, Oct 14, 2014 at 4:08 PM, 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! > > > > I think this process is a little long. > > > > we should freeze new features by the end of this year. then we could > > release 7 asap > > > > and regarding of the qa process, we can use 7.0.x to do that. > > > > thanks > > > Mmmm I don't think it is a good idea to rush the release. > > At the starting point (so, something like one year ago), we had many > ideas to add to the new major PHP and had a compute of at least two > years development. > > Also, we havent talked about a possible PHP 5.7, that could ease the > transition regading BC breaks brought by PHP7, issuing deprecation > notices for examples. > > Also, what about breaks in ABI ? > Have we ported every extension ? Have we written some doc to extension > writters ? Tools for them to ease migration ? > > Last, some big parts - ideas we had - have not been taken in > consideration, nor debatted. Some are listed here : > https://wiki.php.net/ideas/php6/engine > > Quickly put : Asynchronous IO and network code rewriting - PHP/Zend > Extension code rewrite - Introduction of threads into the VM, refactor > TSRM - SPL rewrite and merging .... and many other ideas. > > > Julien.Pauli > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
