Playbooks 07 and 08: a milestone is one delivery group released by one plan; a fix found during it rides in the group #461

2026-10-21T16:05:23Z

mesh-tools commented

2026-10-21 16:05:23 +00:00

The operator decided (2026-10-21, after a day with ten mesh-sdk merges and eight mesh-controller merges): a milestone is one piece of functionality, possibly spanning several modules and repositories and dependencies such as an SDK change. Playbook 07 now says its pull requests in every repository share the milestone's branch name and so form one delivery group (ADR 0482, which holds one group, one plan, one Approve; it builds on ADR 0418, superseded by ADR 0429 on the plan). Nothing merges until every issue of the milestone is built, reviewed and checked; then one Approve and one tiered delivery plan release it all, the tiers keeping a dependency such as the SDK before its dependents. Playbook 08 says a small fix found during a milestone rides in that milestone's group, on its branch, unless what it fixes is broken for the operator now (then it goes alone and the lead's report says why). playbooks.html is updated.

Checked by the lead's report naming the group a fix rides in, and mesh-delivery.deliveries showing the milestone's members in one group and one delivery plan per milestone.

Checks run: records.py, index.py, cycle.py, words.py all pass.

Review record: a playbook edit of a few lines; the operator's Approve of this merge is its review (playbook 08 step 4).

The operator decided (2026-10-21, after a day with ten mesh-sdk merges and eight mesh-controller merges): a milestone is one piece of functionality, possibly spanning several modules and repositories and dependencies such as an SDK change. Playbook 07 now says its pull requests in every repository share the milestone's branch name and so form one delivery group (ADR 0482, which holds one group, one plan, one Approve; it builds on ADR 0418, superseded by ADR 0429 on the plan). Nothing merges until every issue of the milestone is built, reviewed and checked; then one Approve and one tiered delivery plan release it all, the tiers keeping a dependency such as the SDK before its dependents. Playbook 08 says a small fix found during a milestone rides in that milestone's group, on its branch, unless what it fixes is broken for the operator now (then it goes alone and the lead's report says why). playbooks.html is updated. Checked by the lead's report naming the group a fix rides in, and mesh-delivery.deliveries showing the milestone's members in one group and one delivery plan per milestone. Checks run: records.py, index.py, cycle.py, words.py all pass. Review record: a playbook edit of a few lines; the operator's Approve of this merge is its review (playbook 08 step 4).

mesh-tools added 2 commits 2026-10-21 16:05:23 +00:00

Make a small fix in mesh-sdk or mesh-controller ride with the milestone's release, so each is delivered once per milestone c6fc663019

Use the glossary's word for the milestone's branch

mesh/merge-gate building on ace since 18:08

mesh/delivery superseded: a newer head of the same pull request

Details

37a01b93a5

mesh-tools commented

2026-10-21 16:05:34 +00:00

Delivery novox/hq@0162e04f9275 — delivered since 2026-10-21T16:13:05Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-21 16:09 (new) → proposed (announced): novox/hq#461's head announced
2026-10-21 16:11 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-21 16:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-21 16:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-21 16:13 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@0162e04f9275` — **delivered** since 2026-10-21T16:13:05Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-21 16:09 (new) → proposed (announced): novox/hq#461's head announced - 2026-10-21 16:11 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 16:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 16:13 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 16:13 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben added 1 commit 2026-10-21 16:09:01 +00:00

Describe a milestone as one delivery group released by one plan, and make a fix found during it ride in the group

mesh/merge-gate head 0162e04f9275 merged into trunk d5d821220494 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 0162e04f9275 merged into trunk d5d821220494 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

0162e04f92

mesh-tools changed title from ~~Playbook 08: a small fix in mesh-sdk or mesh-controller rides with the milestone's release~~ to Playbooks 07 and 08: a milestone is one delivery group released by one plan; a fix found during it rides in the group

2026-10-21 16:09:10 +00:00

mesh-tools merged commit ac7e445e7a into main

2026-10-21 16:13:04 +00:00

mesh-tools deleted branch playbook/08-release-per-milestone

2026-10-21 16:13:04 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#461