Better visibility for bugs

[GiovanniBussi]

Currently, there might be bugs that are:

• solved on GitHub, hence no open issue is visible
• not yet solved in releases

Usually these bugs are visible at the end of the change log, where one can see what’s changed in the not-yet-released version. There has been some discussion on LinkedIn about how visible these bugs are, I open an issue so that we have a place where we can discuss this topic on GitHub. The specific bug in this case is the one discussed here, but the problem is more general.

Possible options:

• In the download page, add a sentence pointing users to this location (and to GitHub), such as “Known bugs that have not been fixed can be found on GitHub. Known bugs that have been fixed can be found in the linked CHANGES file. Known bugs that are fixed on GitHub but for which the fix has not been released yet can be found at the end of such file.”
• Write these bugs explicitly in the download page, as suggested here. I think this does not scale, because it requires posting the same bug fix twice.
• Keeping issues on GitHub open until the fix percolates to the releases. I an not sure this is a good idea, because it breaks the usual GitHub practice of closing the bug automatically in commit messages.

[Iximiel]

Another option could be pinning a issue, to keep it visible, with the list of the known solved and unsolved bugs, like your first point. And then you can link it (or copy its text with some CI magic, solving the "posting twice the same fix" problem) in a visible section of the site or of the download page.