How do we know this? Was it disclosed? This was a point release so what was the impact to the schedule if they did know? Is a point release really more critical to hit schedule than fix the stopper? If they did know about it and concluded it wasn’t a stopper then that sounds worse than not regression testing in the first instance. I don’t think any outcome makes Apple look clever from this one.
It seems a bit cruel to wish that someone would lose their job (accompanied with all the resulting hardship) over this. It must have been an inconvenience to you and to many other people to deal with this bug, but is it reasonable to attribute the problem to one person in specific, or to make one person take the blame for something Apple might not have known about or fully understood the implications of to begin with? Do you also expect this same level of perfection from your friends, your family and those you deal with in everyday life?
A fired Apple employee will not starve. I don't demand perfection from my family because they don't work for Apple as professionally paid software people. Somebody failed and is responsible that there was field exposure. Apple got lucky that this wasn't a data corruption bug.
OS development is only as complex as what you develop. What they are changing in a point release this late in the development cycle should be fixing bugs and thoroughly testing them. The general expectation of incremental point releases is that the higher the number the less changes involved. That small amount of change should be thoroughly tested, especially if it's to such core service as the HV FW.
You covered it well. Just another observation, MacOS previously Mac OSX really hasn’t had something like this really. It’s core OS was always stable, never mind applications hanging/unexpectedly quitting effected the OS rebooting as far as I remember back to the original X and 10.1.
Jesus. Give it a rest. Both of you. Nobody cares. I’m reading through this thread trying to find salient info about bug fixes, not listen to your rants about whether people should be fired or not. Hopefully a moderator will come in and delete all of these (and this message as well). Thank you.
YGTBFKM! Good catch on the command line Kernel Version date. I can confirm the 19G73, but haven't updated yet to confirm the latter. Anything else you see up(down)dated? Firmware versions?
It’s often the case that Mac OS updates are large - perhaps much larger than you might expect. Doesn‘t necessarily mean a lot has actually changed, and they aren’t going to publish the internals of why.
Seems like anytime you use a different kernel its an another complete install.
I had it happen just once on regular 10.15.6. Just went into displays and reselected color profile.
I can definitely confirm that the synchronisation bug between Apple Mail and iCloud has NOT been resolved by this update, at least not on my iMac...
forums.macrumors.com
Whose heads? The programmer who wrote the code? An individual software tester who failed to catch the bug? The person who wrote the test plan? The QA manager who supervised the testing? The QA director?
