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. 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.
In a small attempt to steer this back on topic,
Does anyone have any problems with python's or gento's enhancement proposals generally? I think they could be made a bit more lightweight but otherwise are pretty useful and transparent.
--
James Butler
Sent from my iPhone
- 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