Thanks for the feedback. Here’s a link to a filtered list of all issues that meet the following criteria:
- Bug affecting 4.3
- Closed as completed between 2025-12-21 (the release date of 4.3.0) and 2026-05-28 (the date of this announcement)
- Was not closed as “cannot reproduce,” “declined,” “duplicate,” “not applicable,” “self-closed,” or “upstream issue”
- Does not pertain to the website, infrastructure, or tests
However, this list still has some limitations:
- It doesn’t exclude documentation issues, because sometimes an issue is about fixing something in the code and in the documentation, and we don’t want to exclude those. However, this means the list might include some pure documentation fixes.
- Bug reports are usually closed as fixed when the relevant PR is merged, but there’s usually a delay before the fix makes it to users’ machines. This means that filtering by date is a very indirect and inexact way to try to capture the correct set of issues (but I don’t have a better one). Some of the fixes in this list might not be available yet, or they might still be in testing.
Now, here are my questions for you and the rest of the Qubes community:
- Is this list useful?
- Is it better than nothing, or does it do more harm than good?
- Should I include this type of link in future announcements like this one?
- Do you see any way to improve the filters?
I understand that a filtered list like this one is less than ideal. The ideal solution would be to have a human (or group of them) go through every single issue that might be relevant to the release, go through all the code changes in each release, and write a curated list of exactly the relevant fixes. Unfortunately, there’s no one available who has the required combination of expertise, time, and willingness to do that. If anyone can think of a better solution, please let us know.