Never cut a milestone by an order between its parts; the delivery plan keeps that order #465

Merged
mesh-tools merged 1 commits from process/07-order-is-the-plans into main 2026-10-21 23:44:17 +00:00
1 Commits
Author SHA1 Message Date
jschoubben 2b857df4b5 Never cut a milestone by an order between its parts: the delivery plan keeps that order from the module graph
mesh/merge-gate head 2b857df4b51e merged into trunk 73a06324dc0d — pass: the change touches no module of the mesh's graph
mesh/repo-check head 2b857df4b51e merged into trunk 73a06324dc0d — pass: its merge-check.sh passed
mesh/delivery delivered
The operator, 2026-10-22: a milestone is a milestone; which module reaches the machines first is what the delivery plan is for. The prepare step still lists every part a change reaches, as issues of the same milestone; an order the plan cannot keep is an issue of the build and delivery system.
2026-10-22 01:30:20 +02:00