Re: PHP 6
| From: | Rasmus Lerdorf | Date: | Sat, 13 Mar 2010 18:13:59 +0000 |
| Subject: | Re: PHP 6 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-47235@lists.php.net to get a copy of this message | ||
On 03/13/2010 08:57 AM, Derick Rethans wrote:
> On Thu, 11 Mar 2010, Rasmus Lerdorf wrote:
>
>> 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.
>
> I am also in favour for getting back to one branch for new development.
> And that "branch" should be trunk. However, I am a little bit reluctant
> to just "kill" all Unicode support. I don't think we can get around the
> fact that propr Unicode support is going to be even more important in
> the future than it already is today. However, we can also not get around
> the fact that the current state of "Unicode-in-PHP" isn't the most ideal
> situation.
You know I am not in favour of "killing" Unicode. We can't kill
Unicode. We live in a Unicode world, like it or not. We just need to
reset the effort and do it in smaller steps. So, setting aside the
current trunk in a branch and slowly bringing the good bits and pieces
from it into the development branch in a way that doesn't alienate
everyone should be the goal here.
> - get rid of Jani's play branch
I don't think Jani has messed up anything in that branch yet, so that
could be the new trunk. It's just cloned from 5.3 exactly like you are
proposing.
> As I now have plenty of time to work on things, I'd be happy to act as
> RM, and wouldn't mind working on roadmaps and sorting out what good bits
> we have/had, and which things we don't want to port back into the new
> trunk. Depending on how things go, this could become 5.4 or 6 or
> something else.
Cool, theoretically I have plenty of time right now as well, although in
practice that doesn't seem to be the case.
-Rasmus