If you care that much about a specific bug, why not file or follow the relevant issue ?
It shows maintainers which are the real issues affecting people, allows two-way communication about the bug, and keeps the changelog clean.
Nodejs is an example of a project that seems to mention every single fixed bug in their changelog, making them so long that I'll probably miss the things that really matter while skimming over them - especially when jumping ahead a few versions.
> It shows maintainers which are the real issues affecting people
I disagree. Sure, it's a signal, but it's quite distorted.
Suppose you have an issue that affects a lot of people, but has a simple workaround. You may not see this issue since no one bothers to file a bug. If in doubt, I'd prefer to fix a papercut that affects 50% of my users vs. a catastrophic show-stopper bug that affects 0.01% of them.
It shows maintainers which are the real issues affecting people, allows two-way communication about the bug, and keeps the changelog clean.
Nodejs is an example of a project that seems to mention every single fixed bug in their changelog, making them so long that I'll probably miss the things that really matter while skimming over them - especially when jumping ahead a few versions.