Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43947 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51738 invoked from network); 14 May 2009 18:49:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2009 18:49:47 -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 204.13.248.71 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 204.13.248.71 mho-01-ewr.mailhop.org Received: from [204.13.248.71] ([204.13.248.71:54109] helo=mho-01-ewr.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 47/6D-27038-AC76C0A4 for ; Thu, 14 May 2009 14:49:47 -0400 Received: from cs181029147.pp.htv.fi ([82.181.29.147] helo=[127.0.0.1]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1M4g00-000EbA-2x; Thu, 14 May 2009 18:49:44 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 82.181.29.147 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+Pm0FsHbb9wQ8DqTlyxsAHz1NQWPbv8tM= Message-ID: <4A0C67C7.1040205@sci.fi> Date: Thu, 14 May 2009 21:49:43 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Ilia Alshanetsky CC: internals Mailing List References: <7033A53F-D4BF-437F-A6AA-AD42C3288342@prohost.org> In-Reply-To: <7033A53F-D4BF-437F-A6AA-AD42C3288342@prohost.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.2.10 From: jani.taskinen@sci.fi (Jani Taskinen) Ilia Alshanetsky kirjoitti: > We have a fair number of fixes in the 5.2 branch already and while 5.3 > is making very good progress I think it is still ways off in terms of > final release and stabilization. I think it makes sense to do one more > 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like > to roll an RC1 by May 28th, so please get your fixes in. Can we add some sort of notice to that release, something like this: "If you did not test a release candidate, any bug report send about issue introduced in this release will automatically be bogus." ?? :D --Jani