Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30534 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33626 invoked by uid 1010); 6 Jul 2007 16:30:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 33610 invoked from network); 6 Jul 2007 16:30:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2007 16:30:03 -0000 Authentication-Results: pb1.pair.com header.from=jani.taskinen@sci.fi; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jani.taskinen@sci.fi; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.171 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 63.208.196.171 outbound.mailhop.org FreeBSD 4.6-4.9 Received: from [63.208.196.171] ([63.208.196.171:3528] helo=outbound.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/F7-50692-80E6E864 for ; Fri, 06 Jul 2007 12:30:02 -0400 Received: from dsl-vsabrasgw1-fe68fb00-185.dhcp.inet.fi ([84.251.104.185] helo=[192.168.0.100]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1I6qgu-0008pQ-LU; Fri, 06 Jul 2007 12:29:56 -0400 X-MHO-User: U2FsdGVkX1/ajKOIyhO9ZG0JcHG8CHscfYCVgWdQPHY= X-MHO-User: U2FsdGVkX19AiG1DbED1F7XJCJMqYXNec0Q7YQNDm0g= X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 84.251.104.185 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18sWkzVj5Kwd8CJaiAOFracjEHsPiwR7NY= Message-ID: <468E6E0E.9020309@sci.fi> Date: Fri, 06 Jul 2007 19:30:06 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Rasmus Lerdorf CC: Derick Rethans , PHP Developers Mailing List References: <468E5AB1.3080308@lerdorf.com> <468E5E3B.5090408@zend.com> <468E66B2.3060903@lerdorf.com> In-Reply-To: <468E66B2.3060903@lerdorf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RIP PHP 4? From: jani.taskinen@sci.fi (Jani Taskinen) Nevermind the wording, just as soon as we just put a notice on php.net that the "end is near, prepare yourselves" the sooner hosting companies, etc. realize the end is really near.. :) I'd be more for dropping all support whatsoever by the end of this year and focus totally on PHP 5/6. Critical security fixes are another issue altogether. --Jani Rasmus Lerdorf kirjoitti: > 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 >