Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89654
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.51 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <56644A03.2030204@php.net>
References: <d7986bddhrs5d7o2c6r42g6h9to3au5kq0@4ax.com>
	<56644A03.2030204@php.net>
Date: Sun, 6 Dec 2015 08:48:16 -0700
Message-ID: <CAFMT4Nr_PbVChuB9-r2gOCyDx0HNNV7qv1=QREHVOpNKgB+0jQ@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] PHP 5.6 life cycle
From: levim@php.net (Levi Morrison)

On Sun, Dec 6, 2015 at 7:45 AM, Sebastian Bergmann <sebastian@php.net> wrote:
> Am 06.12.2015 um 13:14 schrieb Jan Ehrhardt:
>> 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?
>
>  I hope that we stick to the current plan of ending support for PHP 5
>  on 28 Aug 2016. If we don't, then please decide on an EOL date for
>  PHP 5 and announce it ASAP. Lets not repeat the mistakes we made with
>  PHP 4.

I am okay with a date later than 2016-08-28 but I do agree we should
choose the date and stick to it. I do not think we should re-evaluate
adoption of PHP 7 in one year and choose a new EOL for PHP 5 based on
that information. A planned roadmap is better for everyone.