035 — task-plus trials trunk flow on itself (#208)
Status: in progress Roadmap: #199
Why
Stories 032 to 034 built trunk flow behind maturity.flow: trunk, and
every test of it runs against a fake forge and a temporary repository.
#199 deletes the batch, the only release process that has run for real,
and switches every code level 1 project on upgrade.
ADR 0008
gates that on a trial; this is its first half. The story that sets the
key is the first to go through the new process, on the project best
placed to fix what it finds.
What changes
task-plus.yml:maturity.flow: trunk.
Acceptance
| Step | Run by | Outcome |
|---|---|---|
tp story land on this story's branch |
agent | pushed; its pull request opened into main on git.bytestone.uk |
| the pull request merged | human | the fragment is on main; no version, no CHANGELOG change |
tp release query on main |
either | names this story as landed and tp release as the next step |
tp release on main |
human | release/vX.Y.Z pull request opened and merged by tp through the Forgejo API, main tagged, published, installed and the docs deployed; this story's issue closed; the release branch deleted |
A step that fails is the trial's finding: it is fixed, or the key is removed and the repository is back on the batch.
Out of scope
- The second trial, on another project.
- Removing the batch (#199).
Decisions
None.
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