thaloco/aman
1
Fork 0
Code Pull requests Releases Packages Activity Actions

Prepare the 1.0.0 GA release surface

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

6
docs/persona-and-distribution.md
View file

@ -36,7 +36,7 @@ Design implications:
The current release channels are:
1. Current canonical end-user channel: portable X11 bundle (`aman-x11-linux-<version>.tar.gz`).
1. Current canonical end-user channel: portable X11 bundle (`aman-x11-linux-<version>.tar.gz`) published on `https://git.thaloco.com/thaloco/aman/releases`.
2. Secondary packaged channel: Debian package (`.deb`) for Ubuntu/Debian users.
3. Secondary maintainer channel: Arch package inputs (`PKGBUILD` + source tarball).
4. Developer: wheel and sdist from `python -m build`.
@ -75,7 +75,7 @@ variant.
## Release and Support Policy
- App versioning follows SemVer (`0.y.z` until API/UX stabilizes).
- App versioning follows SemVer starting with `1.0.0` for the X11 GA release.
- Config schema versioning is independent (`config_version` in config).
- Docs must always separate:
- Current release channels
@ -86,5 +86,7 @@ variant.
- Daily-use service mode versus manual foreground mode
- Canonical recovery sequence
- Representative validation families
- Public support and issue reporting currently use email only:
`thales@thalesmaciel.com`
- GA means the support contract, validation evidence, and release surface are
consistent. It does not require a native package for every distro.