Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47483
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4BA8EA9C.7030307@lerdorf.com>
Date: Tue, 23 Mar 2010 17:36:02 +0100
Cc: Pierre Joye <pierre.php@gmail.com>,
 Derick Rethans <derick@php.net>,
 PHP Developers Mailing List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <5AD071B3-2A67-4856-8784-34B47A4E56EA@pooteeweet.org>
References: <alpine.DEB.2.00.1003231550080.4153@kossu.derickrethans.nl> <fe05d1541003230911n7e982a8fkf3fa4ca5cff263da@mail.gmail.com> <4BA8EA9C.7030307@lerdorf.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] trunk is alive and open
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 23.03.2010, at 17:21, Rasmus Lerdorf wrote:

> On 03/23/2010 09:11 AM, Pierre Joye wrote:
>> hi,
>>=20
>> I would rather have some kind of rules defined before opening trunk
>> again (or the pandora box). That's what we are discussing right now.
>> May I know why you choosed that now is the right time to do it and
>> declare it open?
>=20
> We have rules.  Large features, write an RFC and we discuss it.  Small
> and obvious improvements follow commit-then-review as before.  We =
don't
> need more complicated rules than that.


Yeah, but I still think it would be a good idea to figure out lets say =
3-5 big time features that we focus on for the next release and a rough =
timeline for the next release.

For example next major release Q2/Q3 2011:
- traits
- bundling APC
- large file and big number support
- ob patch
- unicode improvements (*)

(*) lets see what ideas we come up with, might turn out to be the big =
thing or maybe just a small incremental tweak here and there

regards,
Lukas Kahwe Smith
mls@pooteeweet.org