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

2026-03-12 19:36:52 -03:00

2.7 KiB

Raw Permalink Blame History

Milestone 5: GA Candidate Validation and Release

Why this milestone exists

The final step to GA is not more feature work. It is proving that Aman has a real public release surface, complete support metadata, and evidence-backed confidence across the supported X11 environment.

Problems it closes

The project still looks pre-GA from a trust and release perspective.
Legal and package metadata are incomplete.
Release artifact publication and checksum expectations are not yet fully defined.
The current release checklist does not yet capture all GA evidence.

In scope

Publish the first GA release as 1.0.0.
Add a real LICENSE file.
Replace placeholder maintainer metadata and example URLs with real project metadata.
Publish release artifacts and checksums for the portable X11 bundle.
Keep native .deb and Arch package outputs as secondary artifacts when available.
Publish release notes that describe the supported environment, install path, recovery path, and non-goals.
Document support and issue-reporting channels.
Complete the representative distro validation matrix.
Add explicit GA signoff to the release checklist.

Out of scope

Expanding the GA promise beyond X11.
Supporting every distro with a native package.
New features that are not required to ship and support the release.

Dependencies

Milestones 1 through 4 complete.
Existing packaging and release-check workflows.
Final validation evidence from the representative distro families.

Definition of done: objective

The release version is 1.0.0.
A LICENSE file exists in the repository.
pyproject.toml, package templates, and release docs contain real maintainer and project metadata.
Portable release artifacts and checksum files are published.
The release notes include install, update, uninstall, troubleshooting, and support/reporting guidance.
A final validation report exists for Debian/Ubuntu, Arch, Fedora, and openSUSE.
The release checklist includes and passes an explicit GA signoff section.

Definition of done: subjective

An external evaluator sees a maintained product with a credible release process.
The release feels safe to recommend to X11 users without author hand-holding.
The project no longer signals "preview" through missing metadata or unclear release mechanics.

Evidence required to close

Published 1.0.0 release page with artifacts and checksums.
Final changelog and release notes.
Completed validation report for the representative distro families.
Updated release checklist with signed-off GA criteria.
Public support/reporting instructions that match the shipped product.
Raw validation evidence stored in user-readiness/<linux-timestamp>.md and linked from the validation matrices.

2.7 KiB Raw Permalink Blame History