Clarify the current release channels versus the X11 GA target so the project has an explicit support promise before milestone 2 delivery work begins. Update the README, persona and distribution docs, and release checklist with a support matrix, the systemd --user daily-use path, the manual aman run support path, and the canonical recovery sequence. Mark milestone 1 complete in the roadmap once that contract is documented. Align run, doctor, and self-check help text with the same service and diagnostics language without changing command behavior. Validated with PYTHONPATH=src python3 -m aman --help, PYTHONPATH=src python3 -m aman doctor --help, and PYTHONPATH=src python3 -m aman self-check --help. Excludes generated src/aman.egg-info and prior user-readiness notes.
1.7 KiB
1.7 KiB
Release Checklist
This checklist covers both current releases and the future X11 GA bar. The GA
signoff sections are required for v1.0.0 and later.
- Update
CHANGELOG.mdwith final release notes. - Bump
project.versioninpyproject.toml. - Run quality and build gates:
make release-checkmake check-default-model
- 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)
- Build packaging artifacts:
make package
- Verify artifacts:
dist/*.whldist/*.tar.gzdist/*.debdist/arch/PKGBUILD
- Tag release:
git tag vX.Y.Zgit push origin vX.Y.Z
- Publish release and upload package artifacts from
dist/. - 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 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.