thaloco/aman
1
Fork 0
Code Pull requests Releases Packages Activity Actions
aman/user-readiness
History
Thales Maciel 31a1e069b3
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
2026-03-12 19:36:52 -03:00
..
1773333303.md Archive the initial user readiness review 2026-03-12 15:00:58 -03:00
1773352170.md Close milestone 4 with review evidence 2026-03-12 18:57:57 -03:00
1773354709.md Prepare the 1.0.0 GA release surface 2026-03-12 19:36:52 -03:00
README.md Prepare the 1.0.0 GA release surface 2026-03-12 19:36:52 -03:00

README.md

User Readiness Reports And Validation Evidence

Each Markdown file in this directory is a user readiness report for the project.

The filename title is a Linux timestamp. In practice, a report named 1773333303.md corresponds to a report generated at Unix timestamp 1773333303.

This directory also stores raw manual validation evidence for GA signoff. Use one timestamped file per validation session and reference those files from:

  • docs/x11-ga/portable-validation-matrix.md
  • docs/x11-ga/runtime-validation-report.md
  • docs/x11-ga/ga-validation-report.md