Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79744
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <CABRjmp__TD6PjNTiETgD-jSmLSE4cuj7AoOzQh+zmnp6XN5G=Q@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> <CAH-PCH5SGuk1L+9y4FBYmdC8GP05UOFnw+iupTy+Av65AGJCnw@mail.gmail.com>
 <c4c3b84eb3b5c5e2451ee3c585fd95c2@mail.gmail.com> <EA391654-F731-4B45-9E45-EE780183EEE4@gmail.com>
 <CABRjmp__TD6PjNTiETgD-jSmLSE4cuj7AoOzQh+zmnp6XN5G=Q@mail.gmail.com>
Date: Tue, 16 Dec 2014 21:59:31 +0100
Message-ID: <CAMUwpuQV1ChBM2KhNix8gKZFOTrooaZx7sqzamcnbVxf=g-RJQ@mail.gmail.com>
To: Florian Margaine <florian@margaine.com>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c383e41f248d050a5ba537
Subject: Re: [PHP-DEV] [RFC] PHP 5.7
From: jpauli@php.net (Julien Pauli)

--001a11c383e41f248d050a5ba537
Content-Type: text/plain; charset=UTF-8

On Tue, Dec 16, 2014 at 8:55 PM, Florian Margaine <florian@margaine.com>
wrote:
>
> Hi list,
>
> I think having a minor PHP version for the only sake of adding E_DEPRECATED
> is kind of pointless to be honest. Historically, PHP (or other languages
> for the matter, I'm thinking of python) minor versions have brought new
> features. Adding notices is not a reason for a new version imho.
>
> If what we want are notices, and helping people to migrate to PHP 7, then
> we can create tools for this. For example, python made a tool to help with
> the transition of python 2 to python 3. Go did the same for 0.x to 1.0, if
> my memory serves right. The point of new versions is to include new
> features or bug fixes for the language, static analysis can be done with
> external tools.
>
> The fact that we'll have to maintain one more version is also not something
> to be taken lightly, especially when I see examples of how things progress
> in php-src. (I'm thinking about the recent contributor who gave up.)
>
> Now, if the reason people want PHP 5.7 is to extend PHP 5 lifetime, then
> it's another matter, and the lifetime of existing versions could be
> extended.
>
> Just my $0.02.
>
>
That's a perfectly valid POV I share.

So I sum-up and introduce the dilema :

- We should push people to PHP7 , whatever the way
- We cannot patch 5.6 to add any Warnings-of-any-kind (stable release,
under release process that forbids that)
- Rolling out a 5.7 with *just* Warnings-of-any-kind is silly, see the
topic I just replied to which is valid to me
- Rolling out a 5.7 with Warnings-of-any-kind + some little-or-not new
features cancels point number one

What else ?

Julien.Pauli

--001a11c383e41f248d050a5ba537--