I think you got my point: it is not about a particular bug, it is about the development policy.
How are things developed, how is the QA handled, how is the release process, where are the checklists to review PRs, the announcement texts, test results etc.?:
Proposal for better development policy
- PRs sent in for the components of the main Julia GitHub are only merged, if they will work on all supported OSes
- there is a checklist for releases, containing
- tests for all supported OSes
- all items in the NEWS.md file are tested
- first if all checks are OK, a release will be made
- there is a definition of what a beta release should be (in what state and what should be the outcome of the release), the same for release candidates.
- if an item in News.md is reported not to work, no release is done, until this is fixed or removed from the news/announcement.
- All checklists (release and QA) are publicly visible and are created together with the Julia community