Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47132
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 148.87.113.124 cause and error)
Message-ID: <4B99639B.9030405@oracle.com>
Date: Thu, 11 Mar 2010 13:41:47 -0800
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: internals@lists.php.net
References: <4B9926E8.4080202@lerdorf.com> <4B995F83.1000605@prohost.org>
In-Reply-To: <4B995F83.1000605@prohost.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6
From: christopher.jones@oracle.com (Christopher Jones)



Ilia Alshanetsky wrote:
 > +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.

I'm +1.  Jani's recent 5.3 changes should be reverted, PHP_5_4
rebranched again, and then the fixes/features merged to the new
branch.

I'd also like to see us start a slow deprioritization of 5.2 work.
Instead effort should go into making 5.3 the prefered stable branch.
One specific example is that Test Fest 2010 tests shouldn't be merged
to 5.2.


 >
 > 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
 >>
 >>
 >

-- 
Email: christopher.jones@oracle.com    Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/   Free PHP Book: http://tinyurl.com/UGPOM