Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44483
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain macvicar.net from 97.107.131.220 cause and error)
Cc: Pierre Joye <pierre.php@gmail.com>,
 PHP internals <internals@lists.php.net>
Message-ID: <DFD95E35-FEA2-4EBE-84A9-6A5FDA85CF53@macvicar.net>
To: Lukas Kahwe Smith <mls@pooteeweet.org>
In-Reply-To: <EAD7D00F-5B9F-4D43-9614-589F5BE039D8@pooteeweet.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 26 Jun 2009 20:26:48 +0100
References: <9A46F4B8-E64A-4C3C-B2A5-FC354A3EB71D@pooteeweet.org> <0C2F23C2-D188-4938-B44C-4ED166B934CE@macvicar.net> <fe05d1540906261126k2d6f12fenf5b00b44044614d4@mail.gmail.com> <EAD7D00F-5B9F-4D43-9614-589F5BE039D8@pooteeweet.org>
Subject: Re: [PHP-DEV] post 5.3.0 development
From: scott@macvicar.net (Scott MacVicar)

On 26 Jun 2009, at 19:59, Lukas Kahwe Smith wrote:
> On 26.06.2009, at 20:26, Pierre Joye <pierre.php@gmail.com> wrote:
>
>> On Fri, Jun 26, 2009 at 7:30 PM, Scott MacVicar<scott@macvicar.net>  
>> wrote:
>>> On 26 Jun 2009, at 16:26, Lukas Kahwe Smith wrote:
>>>
>>>> Aloha,
>>>>
>>>> So the last fix is just being prepared for a commit and so we  
>>>> will be
>>>> tagging 5.3.0 soon.
>>>>
>>>> We would like to up hold the commit freeze until 5.3.0 is  
>>>> announced next
>>>> Tuesday.
>>>>
>>>
>>> This freeze that you guys have implemented is frustrating, just  
>>> branch 5_3
>>> into a release branch and Johannes can take selective fixes from  
>>> 5_3 as
>>> needed.
>>>
>>> We all know your reasons for the freeze and agree with it but  
>>> holding up
>>> regular development is a PITA.
>>
>> It is not holding up development. It is about getting a viable  
>> release
>> cycle and to give us the minimum safety to release 5.3.1 in a
>> reasonable time frame. Please explain me what's wrong to allow only
>> bug fixes for this phase?
>>
>> Also please note that we have HEAD for all the developments and new  
>> features.
>
> Exactly.
> I will do my best to track things that need to be merged. Best is to  
> note if something needs to be merged.
>
> But if you all feel it's such a huge burden then you can of course  
> insist on putting the burden on the RMs. The fact of the matter is  
> that our current infrastructure is not fit for providing both sides  
> with an efficient solution.
>

If we're freezing some more after this release for the SVN conversion  
then we could have a pretty cold branch for another week or so.

As I've already said, I agree with only allow verified bug fixes by  
Johannes into 5.3.0. it's this extra bureaucracy that is getting added  
on top that's sucking hard.

I don't want to leave it up to someone else to merge it into 5.3, I  
should be doing it myself. It's possible that things could get  
accidentally missed wen someone else is applying it.

Scott