Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51189
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain metux.de from 82.165.128.25 cause and error)
Date: Mon, 3 Jan 2011 01:55:10 +0100
To: internals@lists.php.net
Message-ID: <20110103005510.GB27395@nibiru.local>
Reply-To: weigelt@metux.de
References: <vmime.4d1e2613.1982.d1d358858a5883c3@zarafa.edigitalresearch.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <vmime.4d1e2613.1982.d1d358858a5883c3@zarafa.edigitalresearch.com>
User-Agent: Mutt/1.4.1i
Subject: Re: [PHP-DEV] [RFC] Release Process
From: weigelt@metux.de (Enrico Weigelt)

* James Butler <james.butler@edigitalresearch.com> wrote:

> As a 'grown up' you should never expect changes to a system
> to just work without testing, any change introduces risk,
> you need to mitigate against that risk by testing. 

True, but applications should be designed in a way that minimizes
the risk of breaks.

> Irrespective of whatever the php release notes say (you did read
> them didn't you), one should run the new version against your
> code in a non-production environment so all the breakages you
> experience get trapped and fixed before they hit your users.

Great. Now you just have to tell me how to do it with thousands
of different webapps from your hosting customers ... ;-o
 

cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------