Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89671
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain paragonie.com from 209.85.215.42 cause and error)
MIME-Version: 1.0
In-Reply-To: <5664AC01.1020602@gmail.com>
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com>
	<90c8ecbc29f8a40a2430306b807a169e@mail.gmail.com>
	<5664AC01.1020602@gmail.com>
Date: Sun, 6 Dec 2015 17:29:05 -0500
Message-ID: <CAKws9z3dcZexuY548KFM3i7jBWivvqtVfgFFNrq7cqSmN5b=Gw@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Zeev Suraski <zeev@zend.com>, Jan Ehrhardt <phpdev@ehrhardt.nl>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11401a80afe1ca0526424429
Subject: Re: [PHP-DEV] PHP 5.6 life cycle
From: scott@paragonie.com (Scott Arciszewski)

--001a11401a80afe1ca0526424429
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 6, 2015 at 4:43 PM, Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> Hi!
>
> > IMHO, I think we need to look at the 5.6 lifecycle very differently fro=
m
> > how we look at 5.5 and earlier.  This is really the 5.x lifecycle as it=
's
> > the last version that's relatively completely painless to upgrade to fr=
om
> > 5.x (especially 5.3 and later).
>
> We could make 5.6 an LTS release with extended support, but the question
> is given the code delta, would all fixes' authors be willing to do
> essentially double work? Would extension authors be willing to maintain
> two branches long-term? And, if that proves to be hard - wouldn't we end
> up with a situation where they choose to only maintain PHP 5 version
> (since it's easier and that's where 90% of people are) and extensions go
> unsupported for PHP 7 for a long time, creating an adoption problem for 7=
?
>
> I do think we probably need to extend the lifetime of 5.6 (and make an
> RFC on it) since I see no way to have everybody to adopt PHP 7 in mere 8
> months, but we should have a defined EOL date ASAP.
> --
> Stas Malyshev
> smalyshev@gmail.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
=E2=80=8BFrom my perspective, people already have until the end of 2017 to =
switch
to PHP 7. =E2=80=8BI think Long Term Support (TM) is generally an anti-patt=
ern that
promotes negligence and makes it harder to ensure people are running the
latest security updates.

Giving everyone until the end of 2017 to update their servers is more than
sufficient.

Scott Arciszewski
Chief Development Officer
Paragon Initiative Enterprises <https://paragonie.com/>=E2=80=8B

--001a11401a80afe1ca0526424429--