Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89679
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKws9z1H9kOrbX7jfZrbnuike=nProjfszkTTos8Bn7StNAzLg@mail.gmail.com>
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com> <90c8ecbc29f8a40a2430306b807a169e@mail.gmail.com>
 <5664AC01.1020602@gmail.com> <CAKws9z3dcZexuY548KFM3i7jBWivvqtVfgFFNrq7cqSmN5b=Gw@mail.gmail.com>
 <5664C221.9040403@gmail.com> <CAKws9z1H9kOrbX7jfZrbnuike=nProjfszkTTos8Bn7StNAzLg@mail.gmail.com>
Date: Sun, 6 Dec 2015 19:44:03 -0500
Message-ID: <CAFi=QfYcm7UoRT8HnqaXhFJHLGgzObuiogVGNOGUPp9E9DDWmg@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Cc: Stanislav Malyshev <smalyshev@gmail.com>, Zeev Suraski <zeev@zend.com>, 
	Jan Ehrhardt <phpdev@ehrhardt.nl>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c37fba8340b50526442866
Subject: Re: [PHP-DEV] PHP 5.6 life cycle
From: oldschooldsl@gmail.com (Adam Howard)

--001a11c37fba8340b50526442866
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree with Scott.  With each extension we only seem to be enabling people
with bad habits.  8 months is almost a full year and more than enough time.

On Sun, Dec 6, 2015 at 6:51 PM, Scott Arciszewski <scott@paragonie.com>
wrote:

> On Sun, Dec 6, 2015 at 6:17 PM, Stanislav Malyshev <smalyshev@gmail.com>
> wrote:
>
> > Hi!
> >
> > > Giving everyone until the end of 2017 to update their servers is more
> > > than sufficient.
> >
> > Sufficient for what? It is a hard fact that people still run 5.3
> > version. In fact, 2/3 of sites run EOLed versions. You can always say
> > they have only themselves to blame, but then I'm not sure what
> > "sufficient" means. Unless adoption patterns change drastically, by the
> > end of 2017 most people will not be running PHP 7. That's not something
> > we can realistically change (unless you have some way of changing those
> > patterns we didn't try yet or they change by themselves somehow). Thus,
> > our choice lies only in whether we support this majority of users in
> > some way
> > =E2=80=8B=E2=80=8B
> > or say "you are on your own now, we don't care about you anymore".
> > --
> > Stas Malyshev
> > smalyshev@gmail.com
> >
>
>
> =E2=80=8BWe should do everything we can to instill a culture of keeping s=
tuff up to
> date. Just because people are going to shoot themselves in the foot doesn=
't
> mean we should supply them with additional ammo.
>
> If 2/3 of sites still run EOLed versions of PHP, all adding a long-term
> support version is going to do is encourage habits of inertia. "Well, 5.6
> was supported until 2020, why can't 7.0.0 be supported until past 2019?
> This isn't fair."
>
> >
> =E2=80=8B
>  or say "you are on your own now, we don't care about you anymore".
>
> Yes, given the lack of a sensible alternative, I think we need to do this=
.
> And then the community needs to, collectively, invest serious effort in
> finding a remotely exploitable vulnerability in any/all EOL'd versions of
> PHP to give a strong incentive to stop running 5.2.x and 5.3.x in 2016.
>
> Scott Arciszewski
> Chief Development Officer
> Paragon Initiative Enterprises <https://paragonie.com/>
> =E2=80=8B
>

--001a11c37fba8340b50526442866--