-
Notifications
You must be signed in to change notification settings - Fork 0
Create release-readiness checklist for first QEMU release candidate #12
Copy link
Copy link
Open
Labels
area: ci-gatesCI, QEMU gates, regression/readiness/release checks.CI, QEMU gates, regression/readiness/release checks.area: docs-contractsDocs, wiki, ABI/API contracts, hardware-readiness wording.Docs, wiki, ABI/API contracts, hardware-readiness wording.needs: validationNeeds validation evidence or gate run.Needs validation evidence or gate run.priority: P1-highHigh-priority work for the current roadmap.High-priority work for the current roadmap.type: taskConcrete engineering task or implementation work.Concrete engineering task or implementation work.
Milestone
Description
Metadata
Metadata
Assignees
Labels
area: ci-gatesCI, QEMU gates, regression/readiness/release checks.CI, QEMU gates, regression/readiness/release checks.area: docs-contractsDocs, wiki, ABI/API contracts, hardware-readiness wording.Docs, wiki, ABI/API contracts, hardware-readiness wording.needs: validationNeeds validation evidence or gate run.Needs validation evidence or gate run.priority: P1-highHigh-priority work for the current roadmap.High-priority work for the current roadmap.type: taskConcrete engineering task or implementation work.Concrete engineering task or implementation work.
Summary
Create a release-readiness checklist for the first QEMU release candidate.
Problem / objective
Release 0.1 should require passing gates, reconciled docs/contracts, explicit hardware/performance caveats, and clear generated-artifact boundaries.
Acceptance criteria
qemu-full-os-rcevidence before release.Validation
make qemu-full-os-rcmake qemu-readiness-gatemake qemu-abi-contractdocs-onlyfor release notes/docs updatesRelevant files
HARDWARE-READINESS.mdcontracts/qemu-rc-v1.jsonscripts/qemu-full-os-rc.py.gitignoreREADME.md