Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79728
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 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: Tue, 16 Dec 2014 17:24:03 +0100
Message-ID: <CAH-PCH5SGuk1L+9y4FBYmdC8GP05UOFnw+iupTy+Av65AGJCnw@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: Levi Morrison <levim@php.net>, Xinchen Hui <laruence@php.net>, Andrea Faulds <ajf@ajf.me>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b6046b4959ab9050a57c9bc
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b6046b4959ab9050a57c9bc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 16, 2014 at 4: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?
>
> I think the likelihood of getting these notices in the hands of people go=
es
> 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.
>
>
as you mentioned distros lock in to a specific micro version, so if we
introduce this deprecated messages in random micro version, we make it less
likely for the users to stumble upon those deprecated messages and it will
be also harder for us to communicate the upgrade path:
compare:
okay, you only have to install PHP 5.7 check out the deprecated messages in
your error logs, fix those and you are ready to upgrade to 7.0
vs
okay, so install 5.6, but make sure that it is >=3D 5.6.x, except for distr=
o
Z, because they bumped the version but only backported the security fixes
but did not include the last deprecated message and if you fixed those
deprecated messages from your error log, you are ready to upgrade to 7.0.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--047d7b6046b4959ab9050a57c9bc--