Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47490
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: <4BA8F365.3010205@lerdorf.com>
Date: Tue, 23 Mar 2010 18:05:42 +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: <D76D86AE-F322-47C2-AFF5-BB9029A06DB7@pooteeweet.org>
References: <alpine.DEB.2.00.1003231550080.4153@kossu.derickrethans.nl> <fe05d1541003230911n7e982a8fkf3fa4ca5cff263da@mail.gmail.com> <4BA8EA9C.7030307@lerdorf.com> <5AD071B3-2A67-4856-8784-34B47A4E56EA@pooteeweet.org> <4BA8F365.3010205@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:59, Rasmus Lerdorf wrote:

> On 03/23/2010 09:36 AM, Lukas Kahwe Smith wrote:
>>=20
>> On 23.03.2010, at 17:21, Rasmus Lerdorf wrote:
>>=20
>>> 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.
>>=20
>>=20
>> 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.
>>=20
>> For example next major release Q2/Q3 2011:
>> - traits
>> - bundling APC
>> - large file and big number support
>> - ob patch
>> - unicode improvements (*)
>>=20
>> (*) 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
>=20
> We don't need timelines right now.  What we need is some hacking time
> and to bring some fun back into PHP development.  It hasn't been fun =
for
> quite a while.  Once we have a body of new interesting stuff, we can
> start pondering releases with a release branch off of trunk that might
> cherry-pick a subset of the work in trunk and you can start making =
your
> lists and setting timelines at that point.


Well .. as you can see from the above list, this is already a backlog of =
fun stuff that is pretty far along. This is why I am saying lets get to =
a release often cycle, where people can work on stuff and be sure to get =
it in at a reasonable timeframe and also prevent stuff like PHP6/PHP5.3 =
from happening again.

And since we are talking about cherry picking features from trunk into =
the next release branch (along with feature branches), we are back to a =
situation where fun hacking can always happen. But imho we have enough =
features on the table that we can start cherry picking now ... of course =
we can still fast track other stuff later on .. but its also not that =
bad that after a release we already have a full pipeline to plan the =
next release.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org