Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30531 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18226 invoked by uid 1010); 6 Jul 2007 15:58:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 18211 invoked from network); 6 Jul 2007 15:58:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2007 15:58:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 207.126.228.149 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 207.126.228.149 rsmtp1.corp.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [207.126.228.149] ([207.126.228.149:41676] helo=rsmtp1.corp.yahoo.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/96-50692-EB66E864 for ; Fri, 06 Jul 2007 11:58:56 -0400 Received: from trainburn-lm-corp-yahoo-com.local (socks1.corp.yahoo.com [216.145.54.158]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l66Fwker078666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jul 2007 08:58:47 -0700 (PDT) Message-ID: <468E66B2.3060903@lerdorf.com> Date: Fri, 06 Jul 2007 08:58:42 -0700 User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Antony Dovgal CC: Derick Rethans , PHP Developers Mailing List References: <468E5AB1.3080308@lerdorf.com> <468E5E3B.5090408@zend.com> In-Reply-To: <468E5E3B.5090408@zend.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RIP PHP 4? From: rasmus@lerdorf.com (Rasmus Lerdorf) Antony Dovgal wrote: > On 06.07.2007 19:07, Rasmus Lerdorf wrote: >> I'm breaking your vote only rule. I don't really understand what >> dropping support means if we will still release security fixes. That's >> the mode we have been in for at least a year, so what would change at >> the end of the year? >> >> Dropping support to me means PHP 4 becomes like PHP 3. No new releases >> for any reason, and I don't think we can realistically do that yet. >> Saying we are dropping support and then continuing on with the status >> quo seems odd to me. > > To me it means in the first place that we can add a canned answer to the > bugtracker which would say "PHP4 is not supported anymore, install PHP5" > and close all PHP4 only reports. > > So no bug-fixes, no releases except for ones fixing critical security > problems. > And even that should be ceased either in say.. 1 or 2 years. When was the last time we did a PHP4-only bug fix? My fear is that the impact of the no-more-support statement is hurt when we qualify it with the fact that nothing is really changing. I'd be more in favour of a statement that put a final death date on it which means no new releases of any sort. We could still say security-fixes only by the end of the year and then death by 08/08/08 or something like that. -Rasmus