I would think that the idea is to support both the "quick glance to see if it's worth updating" and also "let's look if my specific issue has been fixed"

“See if my issue is resolved” is better handled by github. It is where we track them

But "with my issue" I don't mean a Github issue. I might've had a problem and not opened an issue. Sure you could search through the issues, but the changelog is condensed and often we rewrite titles to be more meaningful for someone that has to understand in somewhat more "layman terms", what that PR is about.

I don’t think there’s an obvious answer. A changelog that enumerates everything is too hard to read/absorb. A changelog that overly summerizes is likely to scant.

I'm thinking of multiple use cases and the question you have. • If I'm not too far behind the last release and I just want to resolve the issue, I want to look at changelogs to know if it's worth updating. Then I look for possible workarounds or discussion on the topic if it doesn't seem that the latest release resolves the issue. • If I happen to have a generic issue that pops up and I want to find a resolution for it, again it depends how far from the latest release I'm. If I'm near, I would always first look at the changelog, and only after google search (because a search engine would add a ton of noise anyway...) • If I'm far from the latest release AND I don't want to update, then I'm looking for a workaround.. so google search or search through issues to find the possible discussion around it is the way to go

I dunno? That doesn’t really help me think about it. Partly, I know that changelogs are written by humans, and I don’t really trust them to be accurate. I see them as signaling what the maintainers want to call out. Or they’re really noisy.

Thank you too!