Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89360
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.41 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
In-Reply-To: <DUB128-W228B016631AB396522B21DBA070@phx.gbl>
Date: Tue, 24 Nov 2015 01:12:27 +0100
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <41DCE9DE-2187-476C-A843-71E86C8C15E1@heroku.com>
References: <DUB128-W228B016631AB396522B21DBA070@phx.gbl>
To: Anatol Belski <weltling@outlook.de>
Subject: Re: [PHP-DEV] 7.0.0 release
From: dz@heroku.com (David Zuelke)

On 23.11.2015, at 22:10, Anatol Belski <weltling@outlook.de> wrote:

> So in the end, a solution is wanted. I don't think any opinion is =
allowed to be ignored for such a topic. So options
>=20
> a) release on 26th including all known bug fixes
> b) do RC8, assume there are no bugs, so target 10th for RTM
> c) do RC8, release on 3rd, expect there are no bugs come in
> d) continue issuing release candidates till it's stable enough (needs =
definition of stable and probably an RFC)
>=20
> I would really ask to reach a consent on either a) or c). IMO, the =
options b) and d) are the direct road to curbing 7.0.0.  There is no =
hurry to release just to release, but it is definitely harmful to slow =
down the rise.

My vote (if it matters) goes for c)

It also has the nice side effect of not clashing with ~Black Friday, and =
by next week, the "oh wow Wordpress just moved to Node.js" hype will =
have died down too, giving PHP 7 more of the attention it deserves ;)