#7 "The smart thing would be to keep quiet about it."
I'm intrigued by this. So if the smart thing to do is to keep quiet and rollup several bug fixes in one and then call it a single bug fix.... how do we accurately count the number of actual bugs that Microsoft have released fixes for? That's a rhetorical question as we both know that the answer is that there is absolutely no way for us to know just how many things any 1 patch actually fixes.
Now given that we both know this, I'm curious to know why you're always comparing the number of fixes Microsoft releases compared to someone else (OS X, Linux, some other OSS etc)... Surely it fairly meaningless to compare the NUMBER of patches or even the NUMBER of critical patches if, at the end of the day, you don't know what's in that executable fix that you just downloaded from Windows Update! Sure it may have fixed 1 bug, but it could have just as easily fixed 2 or 3 or maybe even 20 bugs! Sure 20 is going over the top as I can't see anyone bundling more than a couple of fixes together but it does go to illustrate my point.
We'll never see eye to eye on this and that's fine, makes it a little more interesting this way, but I definetely prefer the OSS way of going about bug fixes. i.e. Keep everything in the open, if this means more bug fixes that's fine, as long as I can, at any stage, have a look at exactly what fixes what. That way if I apply a patch and something stops working I'll know what broke it or at least be able to work out what broke it, as opposed to applying some patch which patches more than it says!
|