Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47415
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)
References: <alpine.DEB.2.00.1003161545500.4153@kossu.derickrethans.nl> <76412548-72DE-42D8-979D-9BD52AF754F8@pooteeweet.org> <alpine.DEB.2.00.1003181658240.4153@kossu.derickrethans.nl> <fe05d1541003181021v43bd130ao9febc20009bdfb6d@mail.gmail.com> <slrnhq4prl.k2i.dsp@experimentalworks.net>
Message-ID: <042C5521-4AE9-477A-B182-31D5FFE08207@pooteeweet.org>
To: David Soria Parra <dsp@php.net>
In-Reply-To: <slrnhq4prl.k2i.dsp@experimentalworks.net>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Thu, 18 Mar 2010 21:50:05 +0100
Cc: "internals@lists.php.net" <internals@lists.php.net>
Subject: Re: [PHP-DEV] PHP 5.4 branch and trunk
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 18.03.2010, at 18:48, David Soria Parra <dsp@php.net> wrote:

> On 2010-03-18, Pierre Joye <pierre.php@gmail.com> wrote:
>> On Thu, Mar 18, 2010 at 6:16 PM, Derick Rethans <derick@php.net>  
>> wrote:
>>
>>> I do agree that we need to do major releases more often, but just
>>> setting a time already feels wrong. It's still open source, so it's
>>> ready when it is ready. That of course should not mean that we  
>>> should
>>> keep on adding features endlessly.
>>
>> for releases, avoid commits rushes right before the freeze, etc. As
>> I've been said before already, I'm all for a fixed release cycle, it
>> is then much easier to define clear priorities and roadmaps.
>
> +1. i think having a fixed release cycle has nothing to do with
> being opensource or not but with being more predictable for people
> depending on release dates.

right. and again i think i was quite explict in my original mail that  
common sense still applies. if we have a buggy release we will  
obviously not release it just because. as for having enough to  
actually warrant a release i do not ever remember a time where there  
werent atleast a handful feasible proposals in varying size on the  
table.

regard
Lukas