Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47533 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84611 invoked from network); 23 Mar 2010 23:02:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2010 23:02:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 188.40.37.16 hq1.backendmedia.com Linux 2.6 Received: from [188.40.37.16] ([188.40.37.16:53014] helo=hq1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/31-12746-47849AB4 for ; Tue, 23 Mar 2010 18:02:12 -0500 Received: from localhost (unknown [127.0.0.1]) by hq1.backendmedia.com (Postfix) with ESMTP id 5F5742E30006; Tue, 23 Mar 2010 23:02:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from hq1.backendmedia.com ([127.0.0.1]) by localhost (hq1.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqUYZNxxY9Uu; Wed, 24 Mar 2010 00:02:09 +0100 (CET) Received: from [192.168.0.151] (217-162-131-234.dclient.hispeed.ch [217.162.131.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by hq1.backendmedia.com (Postfix) with ESMTPSA id BEF732E30003; Wed, 24 Mar 2010 00:02:08 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii In-Reply-To: <4BA8F728.4030005@lerdorf.com> Date: Wed, 24 Mar 2010 00:02:07 +0100 Cc: Pierre Joye , Derick Rethans , PHP Developers Mailing List Content-Transfer-Encoding: quoted-printable Message-ID: References: <4BA8EA9C.7030307@lerdorf.com> <5AD071B3-2A67-4856-8784-34B47A4E56EA@pooteeweet.org> <4BA8F365.3010205@lerdorf.com> <4BA8F728.4030005@lerdorf.com> To: Rasmus Lerdorf X-Mailer: Apple Mail (2.1077) Subject: Re: [PHP-DEV] trunk is alive and open From: mls@pooteeweet.org (Lukas Kahwe Smith) On 23.03.2010, at 18:15, Rasmus Lerdorf wrote: > My point is that your eventual list should come from things that have > been committed to trunk and survived review and tests. Sure, its only that many patches and todo items have been lingering = (hello frustration?) because of the trunk situation, because we decided = to then focus on 5.3 etc. Stuff like traits, the OB fixes have been = flying around for a long time and just didnt get the last attention. LFS = and big ints have also been on the roadmap for ages and it seems like at = least for big numbers there is even a patch. If we now spend a few = months to work on fun stuff (which is what we have trunk for) instead of = focusing on getting this stuff finalized we are just delaying these = patches. We all know that when we get towards crunch time we finalize = patches way more quickly, than when we say "oh lets hack on stuff for a = while and see where we get". Again, for "fun development" there is trunk or feature branches. But we = have enough stuff for a new major release right at our finger tips to = start thinking about what our next release should look like instead of = waiting for another 3-6 months which would obviously also imply a delay = of at least 6-9 months (because big new features we come up with in the = next 3-6 months will need their time to make it into trunk as well). So sure lets take until the end of April to think about a set of patches = we want, but please lets not spend the next 3-6 months coming up with = entirely new ideas to put into the next major update. Then again this = might just be a misunderstanding and you are also just talking about = giving some key features a few weeks to make it into trunk and in a = state where we feel fairly certain that we can fix any issues should = there still be any. In conclusion: There should of course be fun in just hacking out cool stuff, but I = think for most developers a big part of the fun is actually seeing your = ideas in a stable release. regards, Lukas Kahwe Smith mls@pooteeweet.org