Part of #54.
Summary
Add a KnownIssues.md at the repo root: a running list of known issues with workarounds, recreation steps, and fixes when available. nodewright has one (KnownIssues.md); this repo does not, and SUPPORT.md (see the SUPPORT issue) links to it.
Adaptation required (content is net-new, not a port)
nodewright's known-issues are operator-specific (uninstall/image-pull behavior). Do not port that content. Seed this file with known issues specific to the packages here (per-package quirks, version-specific gotchas, workarounds), or start it as a documented-empty template if there are none to record yet.
Format per entry (from nodewright):
- A
## <version or package>: <short title> heading
- Problem
- How to recreate
- Temporary workaround
- Potential fix
- Strike through and mark fixed entries with the release that resolved them.
Acceptance
KnownIssues.md exists at the root in the documented format, seeded with current known issues (or an explicit "none currently known" note).- The
SUPPORT.md link to it resolves.
Part of #54.
Summary
Add a
KnownIssues.mdat the repo root: a running list of known issues with workarounds, recreation steps, and fixes when available. nodewright has one (KnownIssues.md); this repo does not, andSUPPORT.md(see the SUPPORT issue) links to it.Adaptation required (content is net-new, not a port)
nodewright's known-issues are operator-specific (uninstall/image-pull behavior). Do not port that content. Seed this file with known issues specific to the packages here (per-package quirks, version-specific gotchas, workarounds), or start it as a documented-empty template if there are none to record yet.
Format per entry (from nodewright):
## <version or package>: <short title>headingAcceptance
KnownIssues.mdexists at the root in the documented format, seeded with current known issues (or an explicit "none currently known" note).SUPPORT.mdlink to it resolves.