Skip to content

Phase 2 — Killer Feature (VMVolumeMigration)

Project: nodewright

Branch: release

Description: Nodewright v0.1.0 release engineering — tag-and-release procedure, release-verify automation, customer install playbooks (online + air-gapped), docs publish to GitHub Pages, supply-chain artifact bundle (cosign + SBOM + SLSA), hardware-lab release-blocker verification, known-issues catalog, bash-DS coexistence playbook, rollback procedure, post-release support.

Story progress

  • ✅ Completed: 23
  • ⏳ Pending: 0
  • 🛑 Blocked: 0

All stories

ID Title Status Notes
REL-01 the pre-flight check runs `scripts/release-preflight ✅ done
REL-02 the tag command is `git tag -s v0 ✅ done
REL-03 the tag triggers ` ✅ done
REL-04 `scripts/release-verify ✅ done
REL-05 `RELEASE-NOTES-v0 ✅ done Authored across iters 10-12 but each stalled before commit (15-min STALL_TIMEOUT
REL-06 the GitHub Release page links to: the operator image, the FIPS image, the Helm chart OCI URL, the Spectro pack URL, the ✅ done
REL-07 the install playbook in `docs/installation ✅ done
REL-08 an offline install variant (`docs/installation-disconnected ✅ done
REL-09 `docs ✅ done
REL-10 the docs site embeds the architecture brief, all BLESSED PRDs (rendered with the critic-log audit trail accessible), the ✅ done
REL-11 `dist/v0 ✅ done
REL-12 `nwctl release verify v0 ✅ done
REL-13 on tag push, `e2e-hardware ✅ done
REL-14 the hardware-runner verification on tag includes: (a) install Nodewright fresh; (b) run csi-clone migration on a real Ku ✅ done
REL-15 the v0 ✅ done
REL-16 `docs/migration/bash-ds-to-v0 ✅ done
REL-17 the migration playbook documents the v0 ✅ done
REL-18 `MIGRATION ✅ done
REL-19 `docs/rollback ✅ done
REL-20 in-flight VMVolumeMigration workflows during a rollback are NOT auto-aborted — they continue under the rolled-back ope ✅ done
REL-21 `docs/runbooks/release/post-release-week-1 ✅ done
REL-22 `docs/support ✅ done
REL-23 v0 ✅ done