Repository navigation
process: keep data-integrity bugs visible until the fix ships in a release #399
Description
Problem
#287 and #371 were closed as "completed" when #377 merged. That fix was then moved from main to the v3 branch (#378), so every v2.x release still has the bug. Anyone who reads the open issues to judge risk will not see it. The CHANGELOG "Known issues" section is correct, but people rarely read it before adopting.
Ask
- Rule: an issue in
data-integrity,corruptionordurabilitystays open until its fix is in a published release. Link the release in the closing comment. - Add a
known-issuelabel, and a pinned "Known issues in the current release" issue that lists each bug with its affected versions, workaround and fix version. - Add a short "Known issues" section near the top of the README that links to the pinned issue.
- For bugs found by users downstream, add the affected version range to the issue title or body.
#371 has been reopened under this rule.
Activity
docs(roadmap): make v2.0.2 the final v2.x release, split v3.0.0/v3.1.0 (
docs: fix unsafe WAL recovery advice and align docs with milestones (#…
release: v2.0.2 — final planned v2.x release