novox/hq
13
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)
mesh/merge-gate head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
Details
mesh/repo-check head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
Details
mesh/delivery superseded: a newer head of the same pull request
Details

Browse Source
This commit is contained in:
jschoubben
2026-10-17 13:45:11 +02:00
parent 1dafc359fe
commit 4872ccdb6b
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/04-build-handoff.md
+2 -2
View File
@@ -44,8 +44,8 @@ A design becomes **milestones**, and each milestone becomes **issues**:
entry in the design. entry in the design.
7. **Flip the status.** `status: in-progress`, `updated:` today; the design change goes through playbook 7. **Flip the status.** `status: in-progress`, `updated:` today; the design change goes through playbook
[08](08-small-fixes.md) (one hq pull request). [08](08-small-fixes.md) (one hq pull request).
8. **Hand each milestone to playbook 07, one at a time.** The milestone is the feature step; its issues are the 8. **Hand each milestone to playbook 07, one at a time.** The milestone is one release of playbook 07; its issues
step's issues; the next milestone starts when the previous one's delivery plan is done. are the release's issues; the next milestone starts when the previous one's delivery plan is done.
9. **On completion of the last milestone**, run the "when something ships" section of playbook 9. **On completion of the last milestone**, run the "when something ships" section of playbook
[02](02-graduation.md). [02](02-graduation.md).
03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
+2 -2
View File
@@ -485,8 +485,8 @@ What the build proves before this design is implemented (research 055's directio
## Milestones ## Milestones
Confirmed by the operator on 2026-10-17 (playbook 04). Each is one feature step of playbook 07; the next starts Confirmed by the operator on 2026-10-17 (playbook 04). Each is one release of playbook 07; the next starts
when the previous one's delivery is done. Each milestone is one release (playbook 07). when the previous one's delivery is done.
| # | Outcome | Acceptance tests | Repositories | Issues | | # | Outcome | Acceptance tests | Repositories | Issues |
|---|---|---|---|---| |---|---|---|---|---|