Hm. That’s very generic and seems to only describe the software behavior from a user perspective. When I’m looking for a change log, I’m thinking of something like this: https://github.com/evcc-io/evcc/releases (came to mind because evcc was the last thing I updated).
Yeah, well, that does sound like a problem. How can I take responsibility for a production environment based on upstream being like “Yeah, we fixed the bug you reported in a solid way, trust us bro.”
It still doesn’t tell us what was changed in the system, just what are the terms to use it. If you’re using your license agreement instead of release notes or changelog to communicate what’s new, you’re doing it wrong.
there are detailed changelogs for almost every single KB on Microsoft’s website
Yup
Here are the changelogs of the latest 23H2 update, and all the smaller incremental updates:
https://support.microsoft.com/en-us/topic/windows-11-version-23h2-update-history-59875222-b990-4bd9-932f-91a5954de434
Microsoft software is well documented
Hm. That’s very generic and seems to only describe the software behavior from a user perspective. When I’m looking for a change log, I’m thinking of something like this: https://github.com/evcc-io/evcc/releases (came to mind because evcc was the last thing I updated).
Except that it’s not an open source product.
Yeah, well, that does sound like a problem. How can I take responsibility for a production environment based on upstream being like “Yeah, we fixed the bug you reported in a solid way, trust us bro.”
I always read details of updates before I do them. Sort of sad to see most people don’t.
Do you also read license agreement?
No, because that doesn’t tell me what they’re changing about the OS.
Idk, we tweak the license agreement when introducing some experimental features
It still doesn’t tell us what was changed in the system, just what are the terms to use it. If you’re using your license agreement instead of release notes or changelog to communicate what’s new, you’re doing it wrong.