Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47131
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ilia.ws designates 209.85.218.216 as permitted sender)
Message-ID: <4B995F83.1000605@prohost.org>
Date: Thu, 11 Mar 2010 16:24:19 -0500
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091223 Lightning/1.0b2pre Thunderbird/3.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <4B9926E8.4080202@lerdorf.com>
In-Reply-To: <4B9926E8.4080202@lerdorf.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6
From: ilia@ilia.ws (Ilia Alshanetsky)

+1. I think we need we need to make "HEAD" a common use branch where
most of the developers trees are at and current HEAD iteration is just
not it.

On 10-03-11 12:22 PM, Rasmus Lerdorf wrote:
> Ah, Jani went a little crazy today in his typical style to force a
> decision.  The real decision is not whether to have a version 5.4 or
> not, it is all about solving the Unicode problem.  The current effort
> has obviously stalled.  We need to figure out how to get development
> back on track in a way that people can get on board.  We knew the
> Unicode effort was hugely ambitious the way we approached it.  There are
> other ways.
>
> So I think Lukas and others are right, let's move the PHP 6 trunk to a
> branch since we are still going to need a bunch of code from it and move
> development to trunk and start exploring lighter and more approachable
> ways to attack Unicode.  We have a few already.  Enhanced mbstring and
> ext/intl.  Let's see some good ideas around that and work on those in
> trunk.  Other features necessarily need to play along with these in the
> same branch.  I refuse to go down the path of a 5.4 branch and a
> separate Unicode branch again.
>
> The main focus here needs to be to get everyone working in the same branch.
>
> -Rasmus
>
>