neil_g said:
im sure thats what they say, id suggest most dont abide by that. look at how many high profile cock ups have happened recently
![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
or they dont bother at all, how many IT depts are fundimentally understaffed. or how many packages have automatic update enabled, slightly messy way to go but thats another topic.
What you're describing is not typical of a well run IT dept. that works to ITIL or equivalent methodology. Having operating in both such environments, I can tell you that no ITIL operation would operate in the sloppy way you've described. As for being poorly staffed, that is the ultimate reason FOR waiting for others to test first!
Going back to beta testing, Microsoft have one of the biggest, if not the biggest beta testing programmes known to man. I have beta tested for Oracle / Sun Microsystems, IBM and countless others and trust me, no amount of beta testing would convince the wise to get on the first bus!
THIS HAS NOTHING TO DO WITH PHONES
Actually, this has everything to do with phones.
What if an update opens a security back door, for an extreme example allowing unauthorised access to your contacts, SMS, photos, email etc? Not possible? think again!
What if you are a corporate user such as us who rely on near 100% reliable 3G and VPN access via 'i' devices, or access to several cloud based services such as hosted Exchange, CRM, or cloud based storage etc?
On the other hand, maybe you are not a business user, but are one of the millions of people in rural parts if the UK who's only access to reliable broadband is via a 3G network.
For some users such as those I have described, their phone (and the services it provides access to) is every bit as important to them as any IT system. For this reason, the risk of a potentially dodgy mobile software update IS critical, therefore I and others always recommend holding off (at least for a few weeks or months). It just makes sense.