this post was submitted on 04 May 2024
794 points (100.0% liked)
memes
15182 readers
4145 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.