Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89715
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error)
To: internals@lists.php.net
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com>
 <11.24.55814.5A495665@pb1.pair.com> <56659949.8080405@gmail.com>
 <56659ABA.5010708@gmail.com>
Message-ID: <5665A087.3040203@lsces.co.uk>
Date: Mon, 7 Dec 2015 15:06:47 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <56659ABA.5010708@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle
From: lester@lsces.co.uk (Lester Caine)

On 07/12/15 14:42, Rowan Collins wrote:
> Rowan Collins wrote on 07/12/2015 14:35:
>> - On what factors will the decision be based? If the reason to delay
>> the decision is lack of information, what information are we planning
>> to use? Are there metrics we can use to make a more objective decision? 
> 
> Come to think, this works the other way as well: if we *do* make a
> decision now, are there factors that would allow the question to be
> reopened? Again, to have any trust in the announced date, people would
> need to know what these were - if the decision is "probably August
> 2017", then that would be no decision at all.

At the current time August 2017 is more than reasonable. That some
distributions produce their own LTS versions, which for example PHP5.4
has become, just passes the onus to the publisher to act if some serious
security problem arises post that date. The PHP developers have already
passed the buck, but I have no doubt if something serious came up which
needed help from PHP developers they would help out? Certainly my PHP5.4
distribution still sees security related updates even today.

The point here is that people reliant on older versions of PHP are not
doing anything wrong, but rather that the official support for that may
not be via PHP direct. I doubt that PHP5.6 will be an LTS candidate in
any case, but we need a version of PHP7.0 well bedded in before it can
be leap frogged and that will hopefully be the situation by August 2016.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk