Readiness markdown structure #42
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TheAnachronism/tt-rss-viewer#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #41
Question
How should the docs/ release-readiness markdown be organized — filename/path, section outline, and how criteria-plus-rationale is presented — so a later implement effort can consume it as the handoff artifact?
Resolution
Path:
docs/1.0-beta-readiness.mdTop-level shape (mvp-spec-like):
Criterion form: each item is a must-line followed by a short why. Concrete must-lines come from later criteria tickets; this ticket locks only the skeleton and presentation rules.
Known issues: live as an inventory section inside the polish bar (not a separate markdown file, not tracker-only).