Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77956
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuSd7Ojhrn4yh53iWzukztqo=jnH9zRnCi1HXRtLRTWkBg@mail.gmail.com>
References: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com>
 <CABBJUpc0T5_bcq+r3DNGyFLhkSdFV-acHzi5nmKWRiW5_vJiYA@mail.gmail.com> <CAMUwpuSd7Ojhrn4yh53iWzukztqo=jnH9zRnCi1HXRtLRTWkBg@mail.gmail.com>
Date: Tue, 14 Oct 2014 16:52:44 +0800
Message-ID: <CABBJUpcCdgYATy6TdhNbRaCaPTZfPpkOk8Kr23HkpkJsPe6aFw@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: PHP 7.0 timeline
From: laruence@php.net (Xinchen Hui)

And:

On Tue, Oct 14, 2014 at 4:46 PM, Julien Pauli <jpauli@php.net> wrote:
> On Tue, Oct 14, 2014 at 10:26 AM, Xinchen Hui <laruence@php.net> wrote:
>> Hey:
>>
>> On Tue, Oct 14, 2014 at 4:08 PM, Zeev Suraski <zeev@zend.com> wrote:
>>> All,
>>>
>>>
>>>
>>> We=E2=80=99ve had some discussions about it during the version name & p=
hpng RFC
>>> processes, and now that 5.6.0 is behind us =E2=80=93 I think it=E2=80=
=99s 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 beli=
eve
>>> it strikes a good balance between early delivery to stay competitive, a=
nd
>>> having enough time to shape a major version.  Given that we=E2=80=99ve =
already made
>>> some very substantial progress towards 7.0 (with phpng, AST, uniform
>>> variable syntax, etc.) =E2=80=93 I think that timeline is very realisti=
c, and
>>> perhaps we can even beat it.  Restating the obvious, new features that
>>> don=E2=80=99t have compatibility implications can always be delivered i=
n minor
>>> versions, i.e. 7.1, 7.2, etc.

we don't need to do all the ideas into PHP7. we will have 7.1, 7.2 eventual=
ly

thanks
>>>
>>>
>>>
>>> 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



--=20
Xinchen Hui
@Laruence
http://www.laruence.com/