Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89705 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23099 invoked from network); 7 Dec 2015 14:16:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2015 14:16:05 -0000 X-Host-Fingerprint: 2.218.134.247 unknown Received: from [2.218.134.247] ([2.218.134.247:1061] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/24-55814-5A495665 for ; Mon, 07 Dec 2015 09:16:05 -0500 Message-ID: <11.24.55814.5A495665@pb1.pair.com> To: internals@lists.php.net References: Date: Mon, 7 Dec 2015 14:16:00 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 2.218.134.247 Subject: Re: PHP 5.6 life cycle From: ajf@ajf.me (Andrea Faulds) Hi, Jan Ehrhardt wrote: > See http://php.net/supported-versions.php > > Will PHP 5.6 go into 'security fixes only' on 28 Aug 2015 with a end of > life on 28 Aug 2016? Or will we be postponing this a couple of months? As others have pointed out, you made a typo. PHP 5.6 goes into 'security fixes only' on 28th August 2016, next year. Its end of life is currently planned for 28th August 2017. That means 5.6 EOL is 20 months and 11 days away. That's more than one and a half years, it should be enough time to upgrade. But with that said, there may be problems. Obviously, a lot of people are still not using 5.6 or 5.5, even if they are unsupported. And while 7.0.0 might be out now, not everything supports it yet. There will be other factors, too, which would make it difficult to upgrade within that time period. However, I'm not sure if extending the release date now is the best idea. 7.0.0 has only been out for four days. We don't know where the ecosystem will be in August 2017 or how many people will have migrated. At this stage, I'm not sure we can assess whether we need an extension. Furthermore, postponing EOL now means reduced pressure to upgrade to 7. If people feel they do not have to move any time soon, perhaps they won't. So, I wonder if it would not be better to wait until nearer the deadline, and see if we need an extension then? Thanks! -- Andrea Faulds http://ajf.me/