Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28079
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <45D9E88B.1020004@zend.com>
Date: Mon, 19 Feb 2007 21:12:27 +0300
User-Agent: Thunderbird 2.0b2 (X11/20070116)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: php-dev <internals@lists.php.net>
References: <45D47062.1010405@zend.com> <45D4DCF3.2050007@zend.com> <45D589C4.402@zend.com> <62103963.20070219184031@marcus-boerger.de>
In-Reply-To: <62103963.20070219184031@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RCs explained (draft)
From: antony@zend.com (Antony Dovgal)

On 02/19/2007 08:40 PM, Marcus Boerger wrote:
>> Release candidates are development packages released to check if any critical
>> problems have slipped into the code during the previous development period.
>> Release candidates are NOT for production use, they are for testing purposes only
>> even though in most cases there are (almost) no differences between the general
>> availability (GA) release and the last RC.
>> You can help us detect problems by installing and testing release candidates
>> on your own (non-production!) server.
> 
> This should read: You can help yourself...

I believe running the test engine and providing us with feedback users help _us_ in the first place.
 
>> Installation problems.
>> First of all, make sure the build process (on *nix only) and installation went fine for you.
>> PHP supports quite a number of operating systems on different platforms and we continue
>> to work on increasing this number.
>> Although, you might encounter some problems during the installation and we would
>> like to know about them.
> 
>> Test engine.
>> When done with the build, please run the test engine by using the 'make test' command
>> and send us the results (hit 'Y' when it asks you whether to send the report).
>> This way we'll receive the required information about your system to fix the problems
>> detected by the test suite (if any).
> 
>> Real-life tests.
>> We would also appreciate if you install the RC on your development server and run
>> your software. This would help us to detect any (unintentional) changes between
>> the release candidates and general releases.
>> Such real-life tests are the most valuable because our test suite obviously cannot
>> cover every possible use case (but we're working on that).


-- 
Wbr, 
Antony Dovgal