Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89667 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68277 invoked from network); 6 Dec 2015 18:59:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Dec 2015 18:59:55 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:54461] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CD/E1-55814-AA584665 for ; Sun, 06 Dec 2015 13:59:55 -0500 Received: from [127.0.0.1] (unknown [82.240.16.115]) (Authenticated sender: flaupretre@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 1534A4B00B3; Sun, 6 Dec 2015 19:58:47 +0100 (CET) To: Zeev Suraski , Nikita Popov , Ferenc Kovacs References: Cc: Jan Ehrhardt , PHP Internals Message-ID: <5664859E.4020702@php.net> Date: Sun, 6 Dec 2015 19:59:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 151206-0, 06/12/2015), Outbound message X-Antivirus-Status: Clean Subject: Re: [PHP-DEV] PHP 5.6 life cycle From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Le 06/12/2015 18:36, Zeev Suraski a écrit : >> The 'sin' of the PHP 4 EOL was - well - >> that we didn't have one for a very long time. An important 'sin' of the PHP 4 EOL is also the massive backport of PHP 5 features during years, which didn't push people to migrate. >> In general, I don't think timelines make sense to commit to before a version >> is released. If for whatever reason a release gets delayed it makes no >> sense that you'd be forced, as a user, for a shorter upgrade cycle. >> Something along the lines of Francois' suggestion - where the lifetime of >> version N-1 relates to the release date of version N is definitely needed, >> and that was the thinking behind the release process timeline to begin with. >> Yes, starting counting from the release date of version N is better. So, instead of giving one additional year of support, what about a guarantee of 2 years of active support on . starting from .0 release date ? That would extend 5.6 active support to Dec 2017, and EOL on Dec 2018, which is a good trade-off, IMHO. Regards François