My organization has always held back new MacOS releases until the IT team completes internal testing and validation. This is pretty typical and enterprises should be used to this.
Bugs aside, new releases may have behavioral changes and that’s true of any OS.
Smart IT departments do this with Windows upgrades too. Even though Microsoft is usually very good about backwards compatibility, it’s always smart to test these things before you upgrade 500 computers.
My organization has always held back new MacOS releases until the IT team completes internal testing and validation. This is pretty typical and enterprises should be used to this.
Bugs aside, new releases may have behavioral changes and that’s true of any OS.
Smart IT departments do this with Windows upgrades too. Even though Microsoft is usually very good about backwards compatibility, it’s always smart to test these things before you upgrade 500 computers.
A few year back it wasn’t rare to find company who were running two years behind windows update.
The fact that 90% of corporate stuff now runs in the browser has alleviated most of the upgrade issue.
Smarter it departments use the developer/beta builds to test this so day one updates shouldn’t be a problem.
People paid good money for this software, they shouldn’t have to get used to this.
The software is free. They bought the device.
Paid good money for a seatbelt, doesn’t mean I’m gonna drive into a tree
Does your seatbelt update mid operation so its function changes?