Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23537
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <446B1FE6.4090803@toggg.com>
Date: Wed, 17 May 2006 15:06:46 +0200
Reply-To: bertrand@toggg.com
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)
MIME-Version: 1.0
To: Greg Beaver <cellog@php.net>
CC: Sebastian Bergmann <sb@sebastian-bergmann.de>, 
	internals@lists.php.net
References: <4468848D.5020602@php.net> <1645696871.20060515204232@marcus-boerger.de> <446916F5.9050804@php.net> <200605160807.13383.phil@dialsolutions.co.uk> <8F732C3B-08BF-4E39-82CB-255D1C75C0EB@prohost.org> <e4cil4$ub9$1@sea.gmane.org> <446B155E.5050002@php.net>
In-Reply-To: <446B155E.5050002@php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP Release Process Sucks
From: bertrand@toggg.com (bertrand Gugger)

Bonjour,
Greg Beaver wrote:
> Sebastian Bergmann wrote:
> 
>>Ilia Alshanetsky wrote:
>>
>>
>>>For every RC we already send an e-mail to about 12 projects asking them
>>>to test their code against the release and let us know of any issues
>>>that come up.
>>
>>
>> Sadly, this does not seem to work. Maybe because nobody from the
>> projects feels responsible?
> 
> 
> Geez tensions are running high.
> 
> I am the tester for PEAR, and I tested the PEAR Installer (I do not test
> the gazillion packages that I don't maintain) and it worked great with
> PHP 5.1.4.  PEAR doesn't use $_POST and I did not detect any errors.
> 
> In the past I have found at least 4 PHP bugs when testing PEAR with PHP.
>  The fact is, most of the bugs I find are found the instant they are
> introduced as I use the CVS of PHP_5_X for my testing.  In fact the
> system is working quite well from my end, but I can't vouch for other
> projects.
> 
> Greg

I've also been working in the same area.

I would like to add that:
PEAR code is often not php5 E_STRICT compatible for the obvious reason 
that we belongs to the real user area , meaning not running only on some 
dream installations but real production machines with all the no-choices 
that induces and furnishing some layers to practical cases.

But that is not the point here.

Even if we use some kind of fork of run-tests , we have a bunch of tests 
  (.phpt and others).
So by release process, it could be a good idea to run them as a whole on 
different installations.
Yes, we would have to shut off E_STRICT for some of them :)
Outer the fact that some packages need some external means , I believe 
it would not be so hard to implement.
History shows we would have trap some bloody stuff if not bugs.

No, no , Greg , it's cool discussion :)
-- 
toggg