> In the case of a essential calendaring component, it would be > reasonable to assume that this would include checking various > critical dates, like Dec 31, Jan 1 for every year and Feb 29, Mar 1 > for leap years
The problem is, so much is "essential." You may be able to find a few things like "the bit that rounds off the corners of the windows" that won't prevent the thing from working, but most of it is essential. You can test a lot of stuff, but, as you say, you can't test everything; at some point you have to trust the quality control of the vendor (cf. Intel math bug--what computer manufacturer tested that? None of them.) To pick this one thing and say that it demonstrates MS's incompetence is ridiculous. Now, are there meetings and memos in Redmond about "Why didn't we catch this and how are we going to prevent it from happening again?" Of course there are. But that is not at all what Tom is getting at, which is that a failure to catch a single bug in a third-party component is proof of massive incompetence. Piffle. ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
