Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Message-ID: <6565068B-2672-4844-8997-36F4523F2A30@pooteeweet.org>
To: PHP Internals <internals@lists.php.net>
In-Reply-To: <98EB8387-02DF-40F0-90A7-058EFBC6B219@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 18 Mar 2009 14:55:04 +0100
References: <1236701064.8652.124.camel@goldfinger> <0B1C8B5E-E06C-4919-885C-ED15A8A53449@pooteeweet.org> <98EB8387-02DF-40F0-90A7-058EFBC6B219@pooteeweet.org>
Subject: Re: [PHP-DEV] Towards 5.3 RC
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 18.03.2009, at 11:06, Lukas Kahwe Smith wrote:

>
> On 17.03.2009, at 10:59, Lukas Kahwe Smith wrote:
>
>>
>> On 10.03.2009, at 17:04, Johannes Schl=FCter wrote:
>>
>>> Hi,
>>>
>>> I wrote a mail last Friday about this but it seems like it got =20
>>> lost. I
>>> wanted to go RC on Thursday, as this now would be a rather short-=20
>>> time
>>> announcement (while quite a few devs already knew) this plan has =20
>>> changed
>>> by a week:
>>>
>>>
>>> PHP 5.3.0 RC 1 is now scheduled for Thursday 2009/03/19.
>>>
>>>
>>> This means we'll enter the pre-build commit-freeze for build fixes =20=

>>> only
>>> on Wednesday 2009/03/18.
>>
>> Just a reminder. This means today is the day to get your fixes in. =20=

>> Is anyone looking over Matt's patches?
>>
>> Also on the wiki are several open todo items:
>> http://wiki.php.net/todo/php53#rc1
>>
>> Please let me know if any items on there are already done.
>> Also let Johannes and myself know of any show stoppers that will =20
>> not get completed today.
>> Remember this is an RC, so we should be quite serious about the =20
>> quality we are releasing.
>>
>> This is the time for bug fixes and _not_ for features. I know there =20=

>> is a certain tendency to put features first, since important open =20
>> bug fixes delay a release, while feature additions at this point =20
>> will not. I ask everybody to pay "fair" and focus on getting PHP =20
>> 5.3 out the door, rather than rushing features in now, that take =20
>> away the focus from bug fixing and worse yet could add new bugs.
>
>
> Ok, since there is too much last minute stuff going on and we are =20
> aiming for a release quality RC1, we have decided to move the =20
> release date to next Tuesday, the 24th.
>
> Bug fixing until this Friday. Any other bug fixing over the weekend =20=

> needs the nod of one of the RMs. Build fixing Monday. Release Tuesday.


At the request of Pierre, I am tightening the commit window.
Please finish all bug fix commits by Thursday.
If there are any last minute discoveries, you can ask Johannes and =20
myself to be allowed to commit on Friday. The later in the day the =20
request comes, the less likely we are to approve the commit.

Anything after that (including commits to the test suite) will need to =20=

be reverted unless its a build fix. Please do not waste time doing =20
reverts. Release candidates need proper QAing ahead of time. In the =20
future we will try to stick with Thursday releases with a commit =20
freeze starting the Tuesday before, to give two full week days of =20
build fixing.

As such it would be appreciated if people can spend some time on the =20
weekend to do as much build fixing as possible to ensure that we can =20
get done on Monday in order to release on Tuesday.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org