thaloco/aman
1
Fork 0
Code Pull requests Releases Packages Activity Actions
aman/docs/x11-ga/portable-validation-matrix.md
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

2.2 KiB
Raw Blame History

Portable Validation Matrix

This document tracks milestone 2 and GA validation evidence for the portable X11 bundle.

Automated evidence

Completed on 2026-03-12:

  • PYTHONPATH=src python3 -m unittest tests.test_portable_bundle
    • covers bundle packaging shape, fresh install, upgrade, uninstall, purge, unmanaged-conflict fail-fast behavior, and rollback after service-start failure
  • PYTHONPATH=src python3 -m unittest tests.test_aman_cli tests.test_diagnostics tests.test_portable_bundle
    • confirms portable bundle work did not regress the CLI help or diagnostics surfaces used in the support flow

Manual distro validation

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
Arch Pending Pending Pending Pending Pending Pending Pending Pending Pending Pending
Fedora Pending Pending Pending Pending Pending Pending Pending Pending Pending Pending
openSUSE Pending Pending Pending Pending Pending Pending Pending Pending Pending Pending

Required release scenarios

Every row above must cover:

  • runtime dependencies installed with the documented distro command
  • bundle checksum verified
  • ./install.sh succeeds
  • systemctl --user enable --now aman succeeds through the installer
  • first launch reaches the normal settings or tray workflow
  • upgrade preserves ~/.config/aman/ and ~/.cache/aman/
  • uninstall removes the command shim and user service cleanly
  • reinstall succeeds after uninstall
  • missing dependency path gives actionable remediation
  • pre-existing distro package or unmanaged shim conflict fails clearly