Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47120
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.226.175.4 cause and error)
Message-ID: <4B9926E8.4080202@lerdorf.com>
Date: Thu, 11 Mar 2010 09:22:48 -0800
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9pre) Gecko/20100309 Shredder/3.0.4pre
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: PHP 6
From: rasmus@lerdorf.com (Rasmus Lerdorf)

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