From b0cfd08f7c97db604b18d34e7b4e7a07bc9f8c77 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 17 Oct 2026 17:20:16 +0200 Subject: [PATCH] Design 47: ADR 0420 accepted, ADR 0249 superseded, milestone 3's issues named (review of #404) --- 03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index 4bdbff21..882e12da 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -5,6 +5,7 @@ code: [mesh-controller, mesh-catalog modules/mesh-delivery] updated: 2026-10-17 decisions: - "ADR 0421" + - "ADR 0420" - "ADR 0419" - "ADR 0418" - "ADR 0408" @@ -33,7 +34,6 @@ decisions: - "ADR 0270" - "ADR 0267" - "ADR 0250" - - "ADR 0249" - "ADR 0239" - "ADR 0238" - "ADR 0233" @@ -549,7 +549,7 @@ when the previous one's delivery is done. |---|---|---|---|---| | 1 | A merge during a running delivery is never dropped and needs no person's release; the merge window lives on the bus; a rollout that shares nothing with an open one runs beside it | 8, 9, 11 | mesh-controller | 973 (with the rest of 525); delivered 2026-10-17 (mesh-controller #366, #367) | | 2 | A ready mark is acted on within seconds, and each pull request has at most one waiting check | 5, 6, 7 | mesh-controller, mesh-catalog (mesh-delivery, gitea) | 974, 975, 976; delivered 2026-10-17 in one plan (mesh-controller #368, mesh-catalog #345) | -| II | phase II: build-agent and route-proxy live whole in mesh-controller, in two releases under ADR 0420 (proposed, not yet in force): release 1 has the controller accept a reviewed move and mesh-delivery announce each merge with its Approve; release 2 is the move | — | mesh-controller, mesh-catalog (mesh-delivery, build-agent, route-proxy) | release 1: 1025; release 2: 1019 | +| II | phase II: build-agent and route-proxy live whole in mesh-controller, in two releases under ADR 0420 (accepted 2026-10-17): release 1 has the controller accept a reviewed move and mesh-delivery announce each merge with its Approve; release 2 is the move | — | mesh-controller, mesh-catalog (mesh-delivery, build-agent, route-proxy) | release 1: 1025; release 2: 1019 | | 3 | A feature with a new seat verb across the controller and the catalogue is one group, one batch, one delivery plan and one Approve: no order lines, no ready mark, each module built and sent once | 1, 6 | mesh-controller, mesh-catalog (mesh-delivery, gitea) | 977, 978, 1022; 605 (1021 closed as its duplicate) is resolved by this build (ADR 0419 §7) | | 4 | A delivery backs up the data it moves first, and a failed backup holds it and is said | 3 | mesh-controller, mesh-catalog (mesh-delivery, the backup seat's holder) | 980 | | 5 | One read of a module on a node names the commit, build and rollout that put it there | 10, 12 | mesh-controller, mesh-catalog (mesh-config, nats) | 981 | @@ -558,7 +558,7 @@ when the previous one's delivery is done. The issues are linked `depends-on` in this order; 976 depends on 975, and 979 also on 971. Phase II is not a milestone of this design's own: it was put before milestone 3 by the operator on 2026-10-17, and its release 2 is opened only once release 1's delivery plan is done. Milestone 3 builds ADR 0418, ADR 0419 and ADR 0421 -(each record's last clause names its issues). Acceptance test 6 spoke of a ready mark when milestone 2 was delivered; restated for +(issues 977, 978 and 1022). Acceptance test 6 spoke of a ready mark when milestone 2 was delivered; restated for the Approve, it is proved again by milestone 3. ## What is not decided here