I don’t have even the remotest clue of what is likely to have gone wrong here .. but just seems to prima facie suggest one more situation where sites in production requiring to have automated test cases to help test all upgrades.

PS : This group seems to have a nice feature indicating the user sentiments – smileys (or should we call it frowneys)

Some interesting snippets : They [.. the bugs ..] are not separate and isolated, they are actually flaws in the process itself. The problems lie within. Only when we acknowledge this (“there is no bug”) and accept it can we hope to affect real change. Agile development is an excellent platform for seamlessly incorporating the required introspection and continual improvement.

and in one of the comments :

“There is no bug” is a good shorthand for the first realization. An agile process lets you more easily respond to the shortcomings (bugs) that will inevitably be found in the implementation of the requirements.

The difference between an average developer and an excellent one is their ability to look past quick-fixes to root causes, and past root causes to systemic, architectural flaws.