044 — At code level 3 the release reads what shipped from the fragments and the forge (#245)
Status: in progress Roadmap: #233
Why
At level 3 a story has no **Status:** line (story 043): its phase is
read from the forge. The release still reads the line. It takes a story
as shipping when its status is ready, stamps it shipped (vX), and
offers a roadmap item as done when every story citing it is ready or
shipped. Without the line none of that happens: a roadmap item whose
stories have shipped is never offered, and an item that became the
story itself is closed by the release yet left unticked until a later
one. The line is not kept at level 1 either: stories 036 to 043 here
all shipped as in progress, so #231 and #232 are still open.
Under trunk flow the release already knows what ships without it: the fragments it gathers name the issues, and it closes them after the tag.
What changes
tp releaseat code level 3: a story ships when a gathered fragment carries its issue, and has shipped when its issue is closed. No story file is stamped.- A roadmap item whose own issue ships is ticked in the release, without a question: at level 3 the item and its story are one issue.
- A roadmap item cited by stories (
**Roadmap:** #N) is offered as done, as today, when every one of them has shipped or ships now. - The plan's
Stories:line names the shipping stories without "stamped shipped". docs/release-workflow.md,docs/roadmap.md.- This repo's roadmap: #231 and #232, shipped in v0.52.0 and v0.53.0, are closed and ticked.
Acceptance
tp release on the base branch at maturity.code: 3:
| Story file | Its issue | Outcome |
|---|---|---|
(#n) on its heading |
in a gathered fragment | ships: named on the plan's Stories: line; its issue closed after the tag; the file not changed |
(#n), with or without a status line |
closed | has shipped |
(#n), status ready |
open, in no fragment | does not ship; the file not stamped |
| Roadmap item #N | Outcome |
|---|---|
| its issue closed | ticked, as today |
| its issue open and in a gathered fragment | ticked in the release commit, no question; closed after the tag with the story it is |
| open, cited by stories that have all shipped or ship now | offered as done; when counted, ticked and closed after the tag |
| open, cited by a story whose issue is open and in no fragment | not offered; unticked |
| open, cited by no story and in no fragment | unticked |
| every item of its epic done by the rows above | the epic leaves whole, as today |
Below level 3 the release reads the status line, as today.
Out of scope
- Level 1, where the status line stays, kept or not.
tp roadmap archiverun by hand: it reads the forge alone, and so ticks an item once its issue is closed.- The batch and the lone release, which level 3 does not have.
Decisions
None recorded as an ADR. An item whose own issue ships is ticked without asking because there is nothing to judge: the release closes that issue in the same run.
Done when
- tests express the acceptance table and pass
- spec updated
- ADR written if a fork was resolved
- roadmap ticked and stamped; changelog entry
- issue closed with a link to the release