Prepare the 1.0.0 GA release surface

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
This commit is contained in:
Thales Maciel 2026-03-12 19:36:52 -03:00
parent acfc376845
commit 31a1e069b3
No known key found for this signature in database
GPG key ID: 33112E6833C34679
28 changed files with 591 additions and 33 deletions

View file

@ -58,3 +58,4 @@ The final step to GA is not more feature work. It is proving that Aman has a rea
- 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.

View file

@ -106,7 +106,12 @@ Any future docs, tray copy, and release notes should point users to this same se
[`first-run-review-notes.md`](./first-run-review-notes.md) plus
[`user-readiness/1773352170.md`](../../user-readiness/1773352170.md).
- [ ] [Milestone 5: GA Candidate Validation and Release](./05-ga-candidate-validation-and-release.md)
Close the remaining trust, legal, release, and validation work for a public 1.0 launch.
Implementation landed on 2026-03-12: repo metadata now uses the real
maintainer and forge URLs, `LICENSE`, `SUPPORT.md`, `docs/releases/1.0.0.md`,
`make release-prep`, and [`ga-validation-report.md`](./ga-validation-report.md)
now exist. Leave this milestone open until the release page is published and
the milestone 2 and 3 validation matrices are filled with linked raw
evidence.
## Cross-milestone acceptance scenarios

View file

@ -0,0 +1,54 @@
# GA Validation Report
This document is the final rollup for the X11 GA release. It does not replace
the underlying evidence sources. It links them and records the final signoff
state.
## Where to put validation evidence
- Put raw manual validation notes in `user-readiness/<linux-timestamp>.md`.
- Use one timestamped file per validation session, distro pass, or reviewer
handoff.
- In the raw evidence file, record:
- distro and version
- reviewer
- date
- release artifact version
- commands run
- pass/fail results
- failure details and recovery outcome
- Reference those timestamped files from the `Notes` columns in:
- [`portable-validation-matrix.md`](./portable-validation-matrix.md)
- [`runtime-validation-report.md`](./runtime-validation-report.md)
## Release metadata
- Release version: `1.0.0`
- Release page:
`https://git.thaloco.com/thaloco/aman/releases/tag/v1.0.0`
- Support channel: `thales@thalesmaciel.com`
- License: MIT
## Evidence sources
- Portable lifecycle matrix:
[`portable-validation-matrix.md`](./portable-validation-matrix.md)
- Runtime reliability matrix:
[`runtime-validation-report.md`](./runtime-validation-report.md)
- First-run review:
[`first-run-review-notes.md`](./first-run-review-notes.md)
- Raw evidence archive:
[`user-readiness/README.md`](../../user-readiness/README.md)
- Release notes:
[`docs/releases/1.0.0.md`](../releases/1.0.0.md)
## Final signoff status
| Area | Status | Evidence |
| --- | --- | --- |
| Milestone 2 portable lifecycle | Pending | Fill `portable-validation-matrix.md` and link raw timestamped evidence |
| Milestone 3 runtime reliability | Pending | Fill `runtime-validation-report.md` and link raw timestamped evidence |
| Milestone 4 first-run UX/docs | Complete | `first-run-review-notes.md` and `user-readiness/1773352170.md` |
| Release metadata and support surface | Repo-complete | `LICENSE`, `SUPPORT.md`, `pyproject.toml`, packaging templates |
| Release artifacts and checksums | Repo-complete | `make release-prep`, `dist/SHA256SUMS`, `docs/releases/1.0.0.md` |
| Published release page | Pending | Publish `v1.0.0` on the forge release page and attach the prepared artifacts |

View file

@ -20,6 +20,9 @@ Completed on 2026-03-12:
These rows must be filled with real results before milestone 2 can be closed as
fully complete for GA evidence.
Store raw evidence for each distro pass in `user-readiness/<linux-timestamp>.md`
and reference that file in the `Notes` column.
| Distro family | Fresh install | First service start | Upgrade | Uninstall | Reinstall | Reboot or service restart | Missing dependency recovery | Conflict with prior package install | Reviewer | Status | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Debian/Ubuntu | Pending | Pending | Pending | Pending | Pending | Pending | Pending | Pending | Pending | Pending | |

View file

@ -34,6 +34,10 @@ Completed on 2026-03-12:
These rows must be filled with release-specific evidence before milestone 3 can
be closed as complete for GA signoff.
Store raw evidence for each runtime validation pass in
`user-readiness/<linux-timestamp>.md` and reference that file in the `Notes`
column.
| Scenario | Debian/Ubuntu | Arch | Fedora | openSUSE | Reviewer | Status | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Service restart after a successful install | Pending | Pending | Pending | Pending | Pending | Pending | Verify `systemctl --user restart aman` returns to the tray/ready state |