> The way you present it, with "good" vs. "bad", suggests that you're arguing for one, not for both, for release announcements instead of release notes. I don'

> The way you present it, with "good" vs. "bad", suggests that you're arguing for one, not for both, for release announcements instead of release notes. I don't think release notes are bad, but I think adopting a release notes style for a release announcement is bad. Similarly, I think adopting a commit message style in release notes is bad. I'll look for ways to clarify this in the article. >> When vendors just publish a terse changelog, it feels like they don't care much about me >That depends on what you mean by terse. "Bug fixes and performance improvements" is terse and careless. A comprehensive list of changes is not necessarily terse. And in a sense, "release announcements include only the most impactful changes" is terse too. When I say "terse" I mean that they describe each individual change tersely. KeePass is an example of a vendor I think publishes release announcements with terse change rundowns, and I think the announcements suffer because of it.[0, 1] When minor changes get the same screen real estate as big new features, it's hard for the reader to recognize the important features because the signal to noise is too high. Out of curiosity, what's your opinion of KeePass release announcements? [0] https://keepass.info/news/n250304_2.58.html https://keepass.info/news/n250304_2.58.html [1] https://keepass.info/news/n240601_2.57.html https://keepass.info/news/n240601_2.57.html