Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23381
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060515094147.02b55a70@zend.com>
Date: Mon, 15 May 2006 09:45:53 -0700
To: Stefan Esser <sesser@php.net>
Cc: PHP internals <internals@lists.php.net>
In-Reply-To: <4468AD19.5020306@php.net>
References: <4468848D.5020602@php.net>
	<7.0.1.0.2.20060515091102.044df950@zend.com>
	<4468AD19.5020306@php.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] PHP Release Process Sucks
From: andi@zend.com (Andi Gutmans)

At 09:32 AM 5/15/2006, Stefan Esser wrote:
>Hello Andi,
> > I don't see why this attack is directed at Zend people working on PHP,
> > where the release process is completely a community driven effort (and
> > last time I checked, no enterprise was involved in that process either).
>Well I don't see why Zend people commit code that obviously broke a key
>functionality without testing it. And then Zend people come out under
>the trees and speak up that our testers are doing bad jobs. It is true
>that obviously NOONE has tested the code, because otherwise it would
>have been seen instantly.

My point was that this has nothing to do with Zend or not Zend. It's 
happened to all of us in the past (except for maybe you) where we 
have commited code that had problems. It's counter-productive to 
attack individuals and/or entities about this especially when 
everyone's working towards the same goal of contributing to PHP.

So people screw up. I prefer having the occasional screw up then less 
people helping out.

Andi