igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

release-0.3.6 plan: the jobs file mirrored into the NEXT folder by hand (publish-jobs.sh does not)

Browse source
This commit is contained in:
igneum-josh 2026-10-05 11:22:37 +01:00
parent 77bde6fb85
commit f6d41211d1
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/plans/release-0.3.6.md
View file

@ -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/<token>/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).