The planner puts the new node-engine and the new controller in one tier for release 6's switch, and orders every other plan as today (issue 1942) #455

2026-10-24T14:36:10Z

mesh-tools commented

2026-10-24 14:36:10 +00:00

Issue 1942, ADR 0539 §11: release 6's switch is one plan, today's controller's last, in which the new node-engine and the new controller share a tier. The version-skew edge and the engine-first default (ADR 0419 §3, §4) always put the controller in a tier of its own. Now a plan whose merge carries the description line Release-switch: 6 AND moves both mesh-host and mesh-controller draws neither edge, and its tier line names ADR 0539 §11 and each edge it overruled (ADR 0419 §5). Any other plan, a plan with the line but without mesh-host, or a line with another value, is ordered exactly as today. Tests 1942/AC1-AC3 fail on main. Try try-1792851999364263602 passed. It is delivered before R6's pull requests open.

Reviewed-by: review-1942@shanks at 44d9d40582
Pushed-by: lead-47@shanks

Issue 1942, ADR 0539 §11: release 6's switch is one plan, today's controller's last, in which the new node-engine and the new controller share a tier. The version-skew edge and the engine-first default (ADR 0419 §3, §4) always put the controller in a tier of its own. Now a plan whose merge carries the description line `Release-switch: 6` AND moves both mesh-host and mesh-controller draws neither edge, and its tier line names ADR 0539 §11 and each edge it overruled (ADR 0419 §5). Any other plan, a plan with the line but without mesh-host, or a line with another value, is ordered exactly as today. Tests 1942/AC1-AC3 fail on main. Try try-1792851999364263602 passed. It is delivered before R6's pull requests open. Reviewed-by: review-1942@shanks at 44d9d40582538b4c099d4d9ab0ea6622f0dbcdda Pushed-by: lead-47@shanks

mesh-tools added 2 commits 2026-10-24 14:36:11 +00:00

Switch plan: engine and controller share one tier when a merge names release 6's switch (issue 1942, ADR 0539 §11) 74bed5a800

Switch: acts only on a plan moving both engine and controller, and only for value 6 (issue 1942)

mesh/delivery delivered

Details

mesh/check checking 44d9d4058253 on 34b105ea88df

44d9d40582

mesh-tools commented

2026-10-24 14:36:17 +00:00

Delivery novox/mesh-controller@44d9d4058253 — delivered since 2026-10-24T15:38:36Z

Delivery plan — builds mesh-controller → novox; no bus step

tier 0: mesh-controller
novox: receives mesh-controller

Machines

mesh-controller on every machine running it: sent

Transitions

2026-10-24 14:36 (new) → proposed (announced): novox/mesh-controller#455's head announced
2026-10-24 14:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-24 14:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-24 15:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-24 15:37 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-24 15:38 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

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

**Delivery** `novox/mesh-controller@44d9d4058253` — **delivered** since 2026-10-24T15:38:36Z **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller **Machines** - mesh-controller on every machine running it: sent **Transitions** - 2026-10-24 14:36 (new) → proposed (announced): novox/mesh-controller#455's head announced - 2026-10-24 14:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-24 14:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-24 15:37 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-24 15:37 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-24 15:38 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 34b105ea88 into main

2026-10-24 15:37:02 +00:00

mesh-tools deleted branch fix/1942-switch-one-tier

2026-10-24 15:37:02 +00:00

mesh-tools referenced this pull request

2026-10-24 16:37:26 +00:00

The bus's user list grants what release 6 uses before the switch, so the new controller, node-engines, assigner and the operator's way back are not refused after it (issue 1945) #456

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#455