Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89648 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15803 invoked from network); 6 Dec 2015 12:44:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Dec 2015 12:44:29 -0000 X-Host-Fingerprint: 85.223.116.227 227-116.citynet.ftth.internl.net Received: from [85.223.116.227] ([85.223.116.227:9616] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F1/E2-08340-CAD24665 for ; Sun, 06 Dec 2015 07:44:29 -0500 To: internals@lists.php.net Date: Sun, 06 Dec 2015 13:44:25 +0100 Message-ID: References: X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 85.223.116.227 Subject: Re: PHP 5.6 life cycle From: phpdev@ehrhardt.nl (Jan Ehrhardt) Jan Ehrhardt in php.internals (Sun, 06 Dec 2015 13:14:57 +0100): >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? Oops. Corrected: Will PHP 5.6 go into 'security fixes only' on 28 Aug 2016 with a end of life on 28 Aug 2017? Or will we be postponing this a couple of months? >BTW: An end-of-life in Dec 2016 will be in line wih the EOL of OpenSSL >1.0.1: "Version 1.0.1 will be supported until 2016-12-31." >http://openssl.org/policies/releasestrat.html Windows users will have a problem then after 2016-12-31. A way out would be to compile PHP 5.6 in 2017 with OpenSSL 1.0.2. -- Jan