Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79690
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.46 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CABBJUpfLCjWCgOUneN2O2M7qP2WBf8OgbVrdB-jm+Fn_dDJvVA@mail.gmail.com>
References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me>
	<CABBJUpfLCjWCgOUneN2O2M7qP2WBf8OgbVrdB-jm+Fn_dDJvVA@mail.gmail.com>
Date: Tue, 16 Dec 2014 00:29:19 -0700
Message-ID: <CAFMT4NrGBi-YpYz_pOgg=BBhymp5Y4Re9XOwnnY47BTiXA5Oxw@mail.gmail.com>
To: Xinchen Hui <laruence@php.net>
Cc: Andrea Faulds <ajf@ajf.me>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
From: levim@php.net (Levi Morrison)

>> There has been some debate about whether to make =E2=80=9CPHP 5.7". I ha=
ve made a very simple RFC. It proposes a final minor version of PHP 5, PHP =
5.7, to be released at the same time as PHP 7, with no new features whatsoe=
ver.
>>
> I am wondering why we need that?  no new features....
>
> I think we can extend 5.6 release cycle to avoid that..

Extending the PHP 5.6 release cycle doesn't give an opportunity to
raise different E_STRICT and E_DEPRECATED messages in preparation for
PHP 7.0. This may or may not be something you value, but it's
something I personally value.