Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79101
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.212.176 as permitted sender)
References: <3d131946349b68aa2ae26dcfeaa5197a@mail.gmail.com>
	<CAH-PCH6HTTcA+Y-UWi_8kZjtMSKRp3sRmRzS3VWdMYwSXgKeJA@mail.gmail.com>
	<2FCFF6B7-53FB-4D56-9296-371374F79C78@zend.com> <CAH-PCH65RsdW6wgTiC77Hb-1_wFXn4TyqJy_3zVJnediY+dUqw@mail.gmail.com>
In-Reply-To: <CAH-PCH65RsdW6wgTiC77Hb-1_wFXn4TyqJy_3zVJnediY+dUqw@mail.gmail.com>
MIME-Version: 1.0
Thread-Index: AQHW1hici1T7auH8zMzcQ6dfWvcMHwGEQhs9AOgacsoCPagUSJw5VXQw
Date: Sat, 22 Nov 2014 09:56:26 +0200
Message-ID: <c3ec0064df9735f78d372f431deb4ccc@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c365e80b849705086de68e
Subject: RE: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline
From: zeev@zend.com (Zeev Suraski)

--001a11c365e80b849705086de68e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ferenc, all,



The RFC has provisions for making the 3rd and 4th milestones move as needed=
:



=E2=80=9CIt's worth noting that the 3rd and 4th milestones will be quality
dependent. If we have evidence that suggests that PHP 7 isn't sufficiently
mature to go into the RC stage in June, or GA in October - we should of
course adjust the timeline accordingly, and not push out a half-baked
release. However, the goal would be to stick as much as possible to the
deadline of new going-into-7.0 RFCs, and strive to follow the timelines for
the 2nd and 3rd milestones as much as possible, to ensure an October 2015
release of PHP 7.0.=E2=80=9D



This language attempts to balance the motivation to get PHP 7.0 out to
market as soon as possible, with the unwillingness to compromise on
quality.  If we end up having to have 4 months of betas/RCs instead of 3 =
=E2=80=93
then we will=E2=80=A6



Zeev





based on that I would say that our average beta+rc release number is around
7, and sometimes the release for a beta/RC can be delayed, so I think that
having only 3 months for the beta+RC period is too optimistic, we should
make that into 4 months at least, we could either push out the ETA for GA
or move back the alpha period by a month.



sorry if this seems to be nitpicking, just trying to put my experiences
into use.



--=20

Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c365e80b849705086de68e--