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
69 lines
2 KiB
Markdown
69 lines
2 KiB
Markdown
# Aman 1.0.0
|
|
|
|
This is the first GA-targeted X11 release for Aman.
|
|
|
|
- Canonical release page:
|
|
`https://git.thaloco.com/thaloco/aman/releases/tag/v1.0.0`
|
|
- Canonical release index:
|
|
`https://git.thaloco.com/thaloco/aman/releases`
|
|
- Support and issue reporting:
|
|
`thales@thalesmaciel.com`
|
|
|
|
## Supported environment
|
|
|
|
- X11 desktop sessions only
|
|
- `systemd --user` for supported daily use
|
|
- System CPython `3.10`, `3.11`, or `3.12` for the portable installer
|
|
- Runtime dependencies installed from the distro package manager
|
|
- Representative validation families: Debian/Ubuntu, Arch, Fedora, openSUSE
|
|
|
|
## Artifacts
|
|
|
|
The release page should publish:
|
|
|
|
- `aman-x11-linux-1.0.0.tar.gz`
|
|
- `aman-x11-linux-1.0.0.tar.gz.sha256`
|
|
- `SHA256SUMS`
|
|
- wheel artifact from `dist/*.whl`
|
|
- Debian package from `dist/*.deb`
|
|
- Arch package inputs from `dist/arch/PKGBUILD` and `dist/arch/*.tar.gz`
|
|
|
|
## Install, update, and uninstall
|
|
|
|
- Install: download the portable bundle and checksum from the release page,
|
|
verify the checksum, extract the bundle, then run `./install.sh`
|
|
- Update: extract the newer bundle and run its `./install.sh`
|
|
- Uninstall: run `~/.local/share/aman/current/uninstall.sh`
|
|
- Purge uninstall: run `~/.local/share/aman/current/uninstall.sh --purge`
|
|
|
|
The full end-user lifecycle is documented in
|
|
[`docs/portable-install.md`](../portable-install.md).
|
|
|
|
## Recovery path
|
|
|
|
If the supported path fails, use:
|
|
|
|
1. `aman doctor --config ~/.config/aman/config.json`
|
|
2. `aman self-check --config ~/.config/aman/config.json`
|
|
3. `journalctl --user -u aman`
|
|
4. `aman run --config ~/.config/aman/config.json --verbose`
|
|
|
|
Reference diagnostics and failure IDs live in
|
|
[`docs/runtime-recovery.md`](../runtime-recovery.md).
|
|
|
|
## Support
|
|
|
|
Email `thales@thalesmaciel.com` with:
|
|
|
|
- distro and version
|
|
- X11 confirmation
|
|
- install channel and Aman version
|
|
- `aman doctor` output
|
|
- `aman self-check` output
|
|
- relevant `journalctl --user -u aman` lines
|
|
|
|
## Non-goals
|
|
|
|
- Wayland support
|
|
- Flatpak or snap as the canonical GA path
|
|
- Native-package parity across every Linux distro
|