From f6d41211d1ffd34b042b7b5b94cdbbc9c97fa329 Mon Sep 17 00:00:00 2001 From: igneum-josh <337424239+igneum-josh@users.noreply.github.com> Date: Mon, 5 Oct 2026 11:22:37 +0100 Subject: [PATCH] release-0.3.6 plan: the jobs file mirrored into the NEXT folder by hand (publish-jobs.sh does not) --- docs/plans/release-0.3.6.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/plans/release-0.3.6.md b/docs/plans/release-0.3.6.md index 9bb174cf8..0aedfc906 100644 --- a/docs/plans/release-0.3.6.md +++ b/docs/plans/release-0.3.6.md @@ -622,3 +622,10 @@ Baseline 10:11:52Z, before the publish: Mac d937c69d app 0.3.6 node 2b6d23ef DAA 0.3.5 node 2.1.0 (the rolled-back 0.3.5 node) DAA 92578 112.1 MH/s; PC 2 1ccfe586 app 0.3.5 DAA 92578 122.3 MH/s; Sam's Mac 3a9bf309 silent 28 min (app 0.3.5, 0.0 MH/s at its last report); PC 37ba0461 app 0.3.5 node 20139145 DAA 92583 2.3 MH/s. A machine counts as updated only when its node reports a DAA score and the miner a hash rate on 0.3.7. + +The update-now job reached only the OLD folder: `publish-jobs.sh` on this branch writes `dl//igneum-jobs.json` +and has no mirror step (checked 10:21Z: the NEXT folder still served the 09:55:44Z file, 48 jobs, without it; the +0.3.6 Mac, packaged on the NEXT folder, could not see the job). The jobs file and its signature were copied into the +NEXT folder by hand (the ship's own mirror step does the same) and the folder deployed once; the NEXT folder served +the 10:17:25Z file with the job from 10:22:2xZ. Item: `publish-jobs.sh --deploy` must write both folders while the +rotation lasts (rotation-phase-2 plan section 4).