Add the repo-side pieces for milestone 5: MIT licensing, real maintainer and forge metadata, a public support doc, 1.0.0 release notes, release-prep tooling, and CI uploads for the full candidate artifact set. Keep source-tree version surfaces honest by reading the local project version in the CLI and About dialog, and cover the new release-prep plus version-fallback behavior with focused tests. Document where raw validation evidence belongs, add the GA validation rollup, and archive the latest readiness review. Milestone 5 remains open until the forge release page is published and the milestone 2 and 3 matrices are filled with linked manual evidence. Validation: PYTHONPATH=src python3 -m unittest discover -s tests -p 'test_*.py'; PYTHONPATH=src python3 -m unittest tests.test_release_prep tests.test_portable_bundle tests.test_aman_cli tests.test_config_ui; python3 -m py_compile src/*.py tests/*.py; PYTHONPATH=src python3 -m aman version
3.4 KiB
3.4 KiB
Release Checklist
This checklist covers the current portable X11 release flow and the remaining
GA signoff bar. The GA signoff sections are required for v1.0.0 and later.
- Update
CHANGELOG.mdwith final release notes. - Bump
project.versioninpyproject.toml. - Ensure model promotion artifacts are current:
benchmarks/results/latest.jsonhas the latestwinner_recommendation.namebenchmarks/model_artifacts.jsoncontains that winner with URL + SHA256make sync-default-model(if constants drifted)
- Prepare the release candidate:
make release-prep
- Verify artifacts:
dist/*.whldist/aman-x11-linux-<version>.tar.gzdist/aman-x11-linux-<version>.tar.gz.sha256dist/SHA256SUMSdist/*.debdist/arch/PKGBUILD
- Verify checksums:
sha256sum -c dist/SHA256SUMS
- Tag release:
git tag vX.Y.Zgit push origin vX.Y.Z
- Publish
vX.Y.Zonhttps://git.thaloco.com/thaloco/aman/releasesand upload package artifacts fromdist/.- Use
docs/releases/1.0.0.mdas the release-notes source for the GA release. - Include
dist/SHA256SUMSwith the uploaded artifacts.
- Use
- Portable bundle release signoff:
README.mdpoints end users to the portable bundle first.docs/portable-install.mdmatches the shipped install, upgrade, uninstall, and purge behavior.make package-portableproduces the portable tarball and checksum.docs/x11-ga/portable-validation-matrix.mdcontains current automated evidence and release-specific manual validation entries.
- GA support-contract signoff (
v1.0.0and later):
README.mdanddocs/persona-and-distribution.mdagree on supported environment assumptions.- The support matrix names X11, runtime dependency ownership,
systemd --user, and the representative distro families. - Service mode is documented as the default daily-use path and
aman runas the manual support/debug path. - The recovery sequence
aman doctor->aman self-check->journalctl --user -u aman->aman run --verboseis documented consistently.
- GA runtime reliability signoff (
v1.0.0and later):
make runtime-checkpasses.docs/runtime-recovery.mdmatches the shipped diagnostic IDs and next-step wording.docs/x11-ga/runtime-validation-report.mdcontains current automated evidence and release-specific manual validation entries.
- GA first-run UX signoff (
v1.0.0and later):
README.mdleads with the supported first-run path and expected visible result.docs/media/settings-window.png,docs/media/tray-menu.png, anddocs/media/first-run-demo.webmare current and linked from the README.docs/x11-ga/first-run-review-notes.mdcontains an independent reviewer pass and the questions it surfaced.aman --helpexposes the main command surface directly.
- GA validation signoff (
v1.0.0and later):
- Validation evidence exists for Debian/Ubuntu, Arch, Fedora, and openSUSE.
- The portable installer, upgrade path, and uninstall path are validated.
- End-user docs and release notes match the shipped artifact set.
- Public metadata, checksums, and support/reporting surfaces are complete.
docs/x11-ga/ga-validation-report.mdlinks the release page, matrices, and raw evidence files.