Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17039
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Thu, 30 Jun 2005 12:10:51 +0200
Message-ID: <20050630121051.32e29690.pierre@dotgeek.org>
References: <5.1.0.14.2.20050629175554.033f08d0@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: 5.1.0 Release Process
From: pierre@dotgeek.org (Pierre-Alain Joye)

On Wed, 29 Jun 2005 18:10:15 -0700
andi@zend.com (Andi Gutmans) wrote:

> Sorry to break up the allow_url_fopen discussion but I think that
> thread is getting a bit old already and definitely clogging up
> the mailing list. (hint hint)
> 
> I'd like to start moving forward with the 5.1.0 release process.
> It seems we are in quite good shape but as we have had many
> patches since Beta 2 we definitely need another Beta. There is
> also an sqlite upgrade coming within a day.
> 
> I suggest to release Beta 3 in a bit over a week (Friday, July
> 8th), and then go into a feature freeze towards RC1. Depending on
> the stability, I'd aim for RC1 within two weeks of the beta
> (branching it off to PHP_5_1) and then start merging Unicode work
> into HEAD. This merge will probably take a couple of weeks and
> will be done mainly by Andrei and Dmitry. At that time, we
> shouldn't disrupt the tree too much as the merge will be quite
> hard.
> 
> As far as PHP_5_0 branch is concerned. We should slowly fade it
> out but I suggest to still commit important fixes as we might
> find ourselves in a situation where we need to release additional
> mini releases (critical bugs, security bugs, etc).
> 
> So to summarize a schedule I suggest:
> a) 5.1.0 Beta 3 Friday, July 8th.
> b) Release & branch 5.1.0 RC1 July 15-22nd
> c) Mid-July start merging Unicode into HEAD. Until end of July
> minimum changes to HEAD.
> 
> I think it's a good balance between releasing a stable 5.1.0 and
> allowing the Unicode support to make good progress and give a
> chance to a larger audience to help out adding Unicode support to
> extensions.

Nice plan thanks :)

I would like to have 5.1 branches. Stopping the developements for
nearly a month for an already feautures freezed release. What's
branche it after beta2?

Regards,

--Pierre