Droid X 2.2 rollout is delayed?

[Martimus]

It's not smart to release large scale, known-broken updates. For a lot of reasons. It's a public relations nightmare (you're saying you want it, and then a patch, but the vast majority will say the opposite: why did you release something known to be broken?).

Micro$oft and Apple do it all the time!!

Beta testing only goes so far and Marketing departments usually pressure Manufacturing to end testing and get the product to market quickly. The quicker it's generating revenue the better most companies like it.

It's sadly a double-edged sword... From an engineering perspective it's crazy to release a product before it's ready. From a marketing standpoint it's better to strike while the iron is hot. You never know what your competitors might be readying for release while you're QC testing a product. From a management standpoint, they want it released quickly, under budget, and perfect!

 

[mwpeck]

It's not smart to release large scale, known-broken updates. For a lot of reasons. It's a public relations nightmare (you're saying you want it, and then a patch, but the vast majority will say the opposite: why did you release something known to be broken?

The feature is currently broken, how is releasing a patch where it is still broken going to change anything? Its like reading a "Known Issues:" section in a driver update, then getting pissed at the company when one of the known issues isn't fixed in the very next driver update.

You also have the bandwidth push of updates, where you have to prep servers, pay for bandwidth costs, and ensure your infrastructure can support tens of thousands of simultaneous connections downloading an update. To push an update knowing you will have to push another one soon is pretty expensive. There's also a large last minute push from the company on any packaged software update doing last minute testing, getting all of the support teams in place, especially for supporting possibly broken software updates, etc.

This is all expensive and time consuming. It's easy, from the consumer standpoint, to say "well gee, they can just release this and patch it later" but it's really very expensive in both dollars and resources to do that.

I thought OTA updates generally took awhile? Sure it is more expensive to release 2 separate patches, but if the patches are going to be released via OTA during a period of a week, why would they have to worry about pushing "tens of thousands" simultaneous connections? Surely there are not millions of Droid X devices out there that would be required to update, and even then, I doubt there would be a high enough demand for the update that they would have to push tens of thousands at a time. Maybe tens of thousands in a day or so, but thats throughout the whole day, not at one time during the day.

I just think they could have handled it better. If in fact it is only being delayed due to exchange issues, NOTHING is going to be broken that isn't already broken, and they are going to please a much larger userbase by pushing the update out on time as opposed to holding it until they do fix the exchange issues to please maybe a few thousand additional users (as opposed to releasing it now and pleasing the entire userbase that doesn't use exchange, while not affecting exchange users in any way regardless).

I am looking at it from a keep your current customers happy standpoint, delaying the update does just the opposite when delaying it is making your majority wait even longer as opposed to giving them the update now while focusing attention afterwards on the exchange issue.

Even if I needed exchange, I would rather have the official 2.2 update with exchange still not working then get a 2nd patch in a month to fix it, then be stuck with 2.1 with exchange not working and have to wait another month for 2.2

 

[somohapian]

The feature is currently broken, how is releasing a patch where it is still broken going to change anything? Its like reading a "Known Issues:" section in a driver update, then getting pissed at the company when one of the known issues isn't fixed in the very next driver update.

You're mistaken. The update is allegedly breaking something new - wiping security protocols from the device.

 

[racinwarrior]

Even if I needed exchange, I would rather have the official 2.2 update with exchange still not working then get a 2nd patch in a month to fix it, then be stuck with 2.1 with exchange not working and have to wait another month for 2.2

exactly my point as well

however a few things to point out.....

we dont know for sure it has been delayed
its still technically late summer

there hasnt been any official word either way and thats what frustrates me. if froyo isnt going to be released until a month from now...fine...just tell me already