Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47405
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Thu, 18 Mar 2010 17:16:30 +0000 (GMT)
To: Lukas Kahwe Smith <mls@pooteeweet.org>
cc: PHP Developers Mailing List <internals@lists.php.net>, 
    Scott MacVicar <scottmac@php.net>, Ilia Alshanetsky <ilia@php.net>, 
    =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@php.net>
In-Reply-To: <76412548-72DE-42D8-979D-9BD52AF754F8@pooteeweet.org>
Message-ID: <alpine.DEB.2.00.1003181658240.4153@kossu.derickrethans.nl>
References: <alpine.DEB.2.00.1003161545500.4153@kossu.derickrethans.nl> <76412548-72DE-42D8-979D-9BD52AF754F8@pooteeweet.org>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] PHP 5.4 branch and trunk
From: derick@php.net (Derick Rethans)

On Tue, 16 Mar 2010, Lukas Kahwe Smith wrote:

> On 16.03.2010, at 16:58, Derick Rethans wrote:
> 
> other stuff:
> http://wiki.php.net/todo/php60
> http://wiki.php.net/todo/backlog

yeah, I know there is other stuff, I was just listing a few examples of 
things I remembered. Both lists require some scrutiny as I can see from 
a quick glance.

> As for unicode, I would like the next release to be planned 
> independently of finding a solution for unicode, but with the clear 
> option that it will be included if we find a good solution in time 
> (like I said I think it would be good to shoot for a final release 
> summer 2011, so beta phase in early 2011).

I do agree that we need to do major releases more often, but just 
setting a time already feels wrong. It's still open source, so it's 
ready when it is ready. That of course should not mean that we should 
keep on adding features endlessly.

> I propose that sort of a 
> unicode working group forms but much less formal than what I make it 
> sound like. I think the discussions can remain on internals@ and 
> hopefully alternative approaches will be documented as RFCs. But what 
> I mean with working group is a list of a handful of names who feel 
> responsible to keep this topic moving until a solution is found and 
> who people know they can contact if they want to chat or whatever.

So how would that "group" differ from just internals@ ?

> Again if these guys find a workable solution that can be implemented 
> this year and I am all for putting it into the next release.

It might also be possible to introduce Unicode step by step. Not 
everything does necessarily have to be done in one release.

regards,
Derick

-- 
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug