Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77952
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com>
References: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com>
Date: Tue, 14 Oct 2014 16:26:14 +0800
Message-ID: <CABBJUpc0T5_bcq+r3DNGyFLhkSdFV-acHzi5nmKWRiW5_vJiYA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: 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)

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 & php=
ng 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 believ=
e
> it strikes a good balance between early delivery to stay competitive, and
> having enough time to shape a major version.  Given that we=E2=80=99ve al=
ready made
> some very substantial progress towards 7.0 (with phpng, AST, uniform
> variable syntax, etc.) =E2=80=93 I think that timeline is very realistic,=
 and
> perhaps we can even beat it.  Restating the obvious, new features that
> don=E2=80=99t 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
>
>
>
> Zeev



--=20
Xinchen Hui
@Laruence
http://www.laruence.com/