Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79734
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <b110fda6282aaf482e7906fcccdb00ab@mail.gmail.com>
References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me>
	<CABBJUpfLCjWCgOUneN2O2M7qP2WBf8OgbVrdB-jm+Fn_dDJvVA@mail.gmail.com>
	<CAFMT4NrGBi-YpYz_pOgg=BBhymp5Y4Re9XOwnnY47BTiXA5Oxw@mail.gmail.com>
	<b110fda6282aaf482e7906fcccdb00ab@mail.gmail.com>
Date: Wed, 17 Dec 2014 04:15:25 +1100
Message-ID: <CAEZPtU66co6+htncLC=fu1C5SanX0HU6pB-_SNJ15YR2y4Bgjg@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>, Andrea Faulds <ajf@ajf.me>, Xinchen Hui <laruence@php.net>, 
	Levi Morrison <levim@php.net>
Content-Type: multipart/alternative; boundary=047d7bf1617e4a4405050a588111
Subject: RE: [PHP-DEV] [RFC] PHP 5.7
From: pierre.php@gmail.com (Pierre Joye)

--047d7bf1617e4a4405050a588111
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Dec 16, 2014 10:23 PM, "Zeev Suraski" <zeev@zend.com> wrote:
>
> > -----Original Message-----
> > From: morrison.levi@gmail.com [mailto:morrison.levi@gmail.com] On
> > Behalf Of Levi Morrison
> > Sent: Tuesday, December 16, 2014 9:29 AM
> > To: Xinchen Hui
> > Cc: Andrea Faulds; PHP Internals
> > Subject: Re: [PHP-DEV] [RFC] PHP 5.7
> >
> > >> There has been some debate about whether to make =E2=80=9CPHP 5.7". =
I have
> > 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
whatsoever.
> > >>
> > > 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 rais=
e
> > 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.
>
> I don't see why we'd need new E_STRICT's, but what stops us from adding
> E_DEPRECATED to 5.6.x?

We do not allow them or we try to avoid them by all means.

> I think the likelihood of getting these notices in the hands of people
goes
> way higher if we put it into 5.6.x, which will be perceived as a bug-fix
> release, than a 5.7.0, which will be perceived as a feature release.

And what will be the work load difference then? Zero. However it will
introduce changes in a patch release that may not be expected as of our
RFC. I am totally opposed to this idea.

--047d7bf1617e4a4405050a588111--