Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77951
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.178 as permitted sender)
MIME-Version: 1.0
Thread-Index: Ac/nhgKQiZ0tGtWAQemSL03i3dcnsA==
Date: Tue, 14 Oct 2014 11:08:17 +0300
Message-ID: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3eb0892840d05055d84eb
Subject: RFC: PHP 7.0 timeline
From: zeev@zend.com (Zeev Suraski)

--001a11c3eb0892840d05055d84eb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

All,



We=E2=80=99ve had some discussions about it during the version name & phpng=
 RFC
processes, and now that 5.6.0 is behind us =E2=80=93 I think it=E2=80=99s t=
ime 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=E2=80=99ve alre=
ady 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, a=
nd
perhaps we can even beat it.  Restating the obvious, new features that
don=E2=80=99t have compatibility implications can always be delivered in mi=
nor
versions, i.e. 7.1, 7.2, etc.



The RFC is at https://wiki.php.net/rfc/php7timeline  - comments welcome!



Zeev

--001a11c3eb0892840d05055d84eb--