I wish not just Apple, but all companies and all devs when doing software updates would provide more details in the patch notes. What in the hell does “bug fixes” mean to me? What bug fixes christ sake, security bugs, a software bug, an issue with Mail or iMessage, etc.?
My first exposure to release/patch notes were BSD's release notes, and it's been all downhill ever since -
those notes were written in clear concise language to quickly impart understanding to other smart people (and, especially given the tendency for most people to use automatic updates, you can pretty well assume the people doing manual updates and reading release notes today are, you know, actually interested in details, and at least somewhat capable of understanding them).
Instead we get "bug fixes and performance improvements" ad infinitum. Or annoying mostly-content-free variations (e.g. there's one app I use occasionally, "Transit", that insists on writing fanciful stories in their notes, with so much enforced whimsy that it's genuinely hard to see the actual changes amongst the foolishness - the latest release talks about Easy-Bake ovens in the first paragraph). Please, don't try to keep me from getting bored,
tell me what has changed.
The release notes don't need to try to sell me on updating (like some on the App Store do), I know the general benefits of running the latest version. They don't need to congratulate me for owning the app or try to sell me the app (I've seen those too). And please don't tell me to look in the app to find what has changed - that just tells me you're too lazy to copy a bulleted list from point A and paste it in point B. Just tell me at least what
kinds of things have changed. Often, there are apps I have kept around, but don't use, because there's a problem (not necessarily a bug, perhaps just something that's overly awkward to use). If your release notes indicate that you've done some work in that area, I may need to take another look.
Annoys the bloody hell out of me. And for any devs that do that, I’d love to know why. I don’t need a massive paragraph in the notes for each bug fix; just a simple sentence would do, like we fixed an issue with mail not syncing properly. That’s certainly more understandable than “bug fixes”.
I expect it comes down to one of two things: (1) laziness/time, they don't want to devote anyone's time for even 15-30 minutes when they could just paste in "bug fixes and performance improvements"
yet again, or (2) concerns that if you tell people what you fixed, they'll misinterpret because they're not smart and will complain about various things like "why did you fix bug X instead of mine?" or "because you changed Y now all my data is gone" (frequently connecting "a thing changed" with "I had a problem" even when the two are completely unrelated).
I have to say, a
lot of release notes these days give an overly smug feeling of the dev patting you on the head and saying "don't worry your pretty little head". I'm not asking for your source code, or what line you changed, but "we fixed a problem with inserting text at the beginning of lines when conditions X and Y were present" can be extremely useful. And most of these shops
have a list of what they fixed already, in their own internal notes. All it takes is a few minutes for someone with language skills to summarize those and in some cases tone down details (e.g. people outside the company don't need to know source file or component names, just what the changes look like to end users).