Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23444
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Tue, 16 May 2006 08:07:13 +0100
User-Agent: KMail/1.8.2
Cc: Lukas Smith <lsmith@php.net>
References: <4468848D.5020602@php.net> <1645696871.20060515204232@marcus-boerger.de> <446916F5.9050804@php.net>
In-Reply-To: <446916F5.9050804@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200605160807.13383.phil@dialsolutions.co.uk>
Subject: Re: [PHP-DEV] PHP Release Process Sucks
From: phil@dialsolutions.co.uk (Phil Driscoll)

On Tuesday 16 May 2006 01:04, Lukas Smith wrote:
> That being said .. if there are any additions people have to give better
> guidelines for RM's please drop a comment at the following address:
> http://oss.backendmedia.com/ReleaseChecklist

I've just added the following comment, which addresses part of the problem:
--------------------
Somewhere between the RC and the release, the release manager should
receive email confirmation from a number of volunteers that the RC has
been tested not only with 'make test', but on real world applications such
as the volunteers' own code and high profile applications such as
phpMyAdmin, SquirrelMail and so on.

The RC should not become a release until such confirmation is received.
--------------------

I hereby volunteer to do my code, phpMyAdmin and SquirrelMail for php5 RCs.

Clearly, for this to have maximum impact we need to cover as many 
applications, platforms and SAPIs as possible.
-- 
Phil Driscoll