Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4BAA33D0.7090807@lerdorf.com>
Date: Fri, 9 Apr 2010 23:10:43 +0200
Cc: Felix De Vliegher <felix.devliegher@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <FE584E2C-4730-4B17-A20F-CDFAB9EE1FD2@pooteeweet.org>
References: <40024065-211A-4089-B5A3-E2362FEB0EF5@gmail.com> <4BAA33D0.7090807@lerdorf.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] Open PHP6/trunk bugs
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 24.03.2010, at 16:46, Rasmus Lerdorf wrote:

> On 03/24/2010 08:09 AM, Felix De Vliegher wrote:
>> Hi
>>=20
>> 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?"
>>=20
>> 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?
>=20
> 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.


was anything done here yet?
i presume someone could just change the version to =
"PHP6-First-Experiment" or something on the database ..

regards,
Lukas Kahwe Smith
mls@pooteeweet.org