Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47566 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3520 invoked from network); 24 Mar 2010 15:46:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Mar 2010 15:46:33 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.220.224 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.220.224 mail-fx0-f224.google.com Received: from [209.85.220.224] ([209.85.220.224:41475] helo=mail-fx0-f224.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 59/2F-33174-8D33AAB4 for ; Wed, 24 Mar 2010 10:46:33 -0500 Received: by fxm24 with SMTP id 24so2345451fxm.23 for ; Wed, 24 Mar 2010 08:46:29 -0700 (PDT) Received: by 10.102.216.24 with SMTP id o24mr819073mug.67.1269445589578; Wed, 24 Mar 2010 08:46:29 -0700 (PDT) Received: from [192.168.200.22] (c-98-234-184-167.hsd1.ca.comcast.net [98.234.184.167]) by mx.google.com with ESMTPS id i5sm1006334mue.49.2010.03.24.08.46.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 24 Mar 2010 08:46:27 -0700 (PDT) Message-ID: <4BAA33D0.7090807@lerdorf.com> Date: Wed, 24 Mar 2010 08:46:24 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100323 Shredder/3.0.5pre MIME-Version: 1.0 To: Felix De Vliegher CC: PHP internals References: <40024065-211A-4089-B5A3-E2362FEB0EF5@gmail.com> In-Reply-To: <40024065-211A-4089-B5A3-E2362FEB0EF5@gmail.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Open PHP6/trunk bugs From: rasmus@lerdorf.com (Rasmus Lerdorf) On 03/24/2010 08:09 AM, Felix De Vliegher wrote: > Hi > > Ulf already indicated this in a bug report, but I'd like to bring it up here too: > "There's no PHP 6 any more. What shall happen to those reports: close, bogus, test against 5.3, test against new trunk?" > > There's a lot of open PHP6 / SVN snaps bugs, some of them obviously not valid anymore with the current trunk (e.g. some unicode engine bugs). Do we leave those bugs open for a while until the new unicode initiative has been started? For other bugs, we should probably check if they're still valid and otherwise close, no? We should probably leave them for now. We could change the name somehow, but some of the PHP6 code is likely to resurface in trunk at some point and it doesn't make sense to lose this feedback. -Rasmus