Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64231 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91916 invoked from network); 10 Dec 2012 14:32:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Dec 2012 14:32:03 -0000 Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 217.114.211.66 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:54798] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/06-60401-262F5C05 for ; Mon, 10 Dec 2012 09:32:03 -0500 Received: from [192.168.2.20] (host-188-174-210-58.customer.m-online.net [188.174.210.58]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 08A4F6505C; Mon, 10 Dec 2012 15:31:59 +0100 (CET) To: Pierre Joye Cc: PHP internals list In-Reply-To: References: <1355137083.3178.24.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Organization: PHP Development Team Date: Mon, 10 Dec 2012 15:32:39 +0100 Message-ID: <1355149959.3178.52.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.3 - end of live schedule From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Mon, 2012-12-10 at 14:10 +0100, Pierre Joye wrote: > There was no consensus, I am not sure where you get the idea. By spending the time to go through the thread, taking the opinions stated there, filtering out side discussions (like LTS based release models etc) evaluating it (partly subjective) and summarizing it as in the mail starting this thread. > However, we discussed to wait a bit before proposing the RFC to > clearly and cleanly define the EOL of 5.3. Your message saying "5.4 was released on March, 1st. That's why I asked this question now while it should have been done before." which is one of the last from the thread doesnt' sound like delaying for additional 3/4 years for a decision. > I will clean up this RFC and call for vote later this week (most > likely tomorrow). It is very important to follow this step instead of > simply say, hey, I will go down this way because I like it ;-) feel free to do what you want. > The delay is way too short for 3rd parties to adapt. If people can provide reasons to extend it I'm open to hear those. johannes