Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58500 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12855 invoked from network); 2 Mar 2012 16:04:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 16:04:34 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.42 mail-qw0-f42.google.com Received: from [209.85.216.42] ([209.85.216.42:61942] helo=mail-qw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8C/65-20106-19FE05F4 for ; Fri, 02 Mar 2012 11:04:34 -0500 Received: by qaui11 with SMTP id i11so327979qau.8 for ; Fri, 02 Mar 2012 08:04:31 -0800 (PST) Received-SPF: pass (google.com: domain of tyra3l@gmail.com designates 10.229.135.11 as permitted sender) client-ip=10.229.135.11; Authentication-Results: mr.google.com; spf=pass (google.com: domain of tyra3l@gmail.com designates 10.229.135.11 as permitted sender) smtp.mail=tyra3l@gmail.com; dkim=pass header.i=tyra3l@gmail.com Received: from mr.google.com ([10.229.135.11]) by 10.229.135.11 with SMTP id l11mr1401060qct.140.1330704271119 (num_hops = 1); Fri, 02 Mar 2012 08:04:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sdIQWrW02e7aVdy2i+VwIDTn2RVXoiqP04j0ZKAvYbg=; b=sghtr8cn4TqL/etTMHI21Eddd0j7wkLOL9SGCG4R4/TVqfsjj3GQeSNVYJvjCIGT9h BzY5lewkvI5lZUjnrTH2fFLSyjG68k9lc3h5DfcplZjUKneBdw0EaPlemQG9DDPNJ+Pa NmJUXOrNHfsHuXiPk6Q7s+DeYADuaq2VmEMSZ2rwJFP62BU6TPGBAwpHfM3U8VqXiDQN +XBvWd4+qppdDPa2DN3L1B+Z8bsfGWzUnMmBDawdl+qMs/3w1ztgIqwUfc+XIOrbadVo VwMTNZr2iLcwkySW/7v4xbw8XvKe6HE/L1T/gWdFpFyhE6V1qblsh42rHUB1DMO5X90X 6wCw== MIME-Version: 1.0 Received: by 10.229.135.11 with SMTP id l11mr1197253qct.140.1330704270994; Fri, 02 Mar 2012 08:04:30 -0800 (PST) Received: by 10.229.232.207 with HTTP; Fri, 2 Mar 2012 08:04:30 -0800 (PST) In-Reply-To: References: <4F50EA41.1080706@php.net> Date: Fri, 2 Mar 2012 17:04:30 +0100 Message-ID: To: Pierre Joye Cc: Sebastian Bergmann , internals@lists.php.net Content-Type: multipart/alternative; boundary=00248c7119fd5fae6804ba44bb17 Subject: Re: [PHP-DEV] [RFC] discussions, about a 5.3 EOL From: tyra3l@gmail.com (Ferenc Kovacs) --00248c7119fd5fae6804ba44bb17 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Mar 2, 2012 at 4:54 PM, Pierre Joye wrote: > hi Sebastian, > > On Fri, Mar 2, 2012 at 4:41 PM, Sebastian Bergmann > wrote: > > On 03/02/2012 07:34 AM, Pierre Joye wrote: > >> > >> https://wiki.php.net/rfc/php53eol > > > > > > I discussed with Arne Blankerts and Stefan Priebsch over breakfast tod= ay > > and Stefan had an interesting idea: why not announce (now) that PHP 5.= 3 > > will go into EOL a year after PHP 5.5 comes out? > > And when do you think it is one year after php-next? In two years. So > much about one year being the only option ;-) > > that's just the schedule, if the php-next is being late(which can happen, 3-4 additional RC can cause a 2 month delay), that will force us to either prolong the support of php-old (which would be in contrast with the RFC) or the dates would start shifting apart. if the next-next is also delayed 2 month, then it will be only an 8 months gap between the release of php-next and the EOL of php-old, and I think that would be a trend, because projects tend to being late. so I would support Sebastian's proposal, and there are other projects doing this kind of schedule (debian and fedora comes to mind, but I'm sure there are plenty of others) --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --00248c7119fd5fae6804ba44bb17--