VMware CEO Paul Maritz blogs about the Update 2 BUG
August 13th, 2008 | 
Author: As I mentioned in my post My thoughts on the reactions to the ESX 3.5 Update 2 BUG VMware has been straightforward and honest about their responsibility for the time bomb mistakenly left in their code. VMware’s new CEO, Paul Maritz, has provided another example of this with his blog post VMware: The Console: Letter from VMware CEO Paul Maritz. Read the whole post, but here’s some of the letter I find informative and worth repeating:
“The issue was caused by a piece of code that was mistakenly left enabled for the final release of Update 2. This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.
In remedying the situation, we’ve already released an express patch for those customers that have installed/upgraded to ESX or ESXi 3.5 Update 2. Within the next 24 hours, we also expect to issue a full replacement for Update 2, which should be used by customers who want to perform fresh installs of ESX or ESXi.
I am sure you’re wondering how this could happen. We failed in two areas:
- Not disabling the code in the final release of Update 2; and
- Not catching it in our quality assurance process.
We are doing everything in our power to make sure this doesn’t happen again. VMware prides itself on the quality and reliability of our products, and this incident has prompted a thorough self-examination of how we create and deliver products to our customers. We have kicked off a comprehensive, in-depth review of our QA and release processes, and will quickly make the needed changes.
I want to apologize for the disruption and difficulty this issue may have caused to our customers and our partners. Your confidence in VMware is extremely important to us, and we are committed to restoring that confidence fully and quickly.
Thank You,
Paul Maritz
President and CEO
VMware”
Related Posts
Posted in 
Tags: -
Lukas Beeler
