Contact
Release feedback is most useful when it is specific.
If a build fails, a machine behaves differently than expected, or a release fixed something important for your hardware, send the details with enough context to reproduce the result.
Direct project contact
Use email for release feedback, hardware validation summaries, or project questions that do not fit neatly into a public issue.
GitHub
Underlying disk engine is public
The underlying AmigaDiskKit GitHub repository is available now and reflects the native disk and file-access layers behind newer Amiga Imager workflows.
For reproducible bugs, regressions, and release feedback, please use email and include enough detail to follow the exact build path and hardware result.
Include this
What makes a report actionable
- Amiga Imager version and target platform
- Machine, accelerator, RTG card, and network card details
- AmigaOS source version and any optional packages enabled
- Build log from
~/Library/Logs/Amiga-Imager/
Best signal
Hardware validation is especially valuable
If a release works on real hardware, send the exact setup and result. Confirmed boots and confirmed failures are both useful when they narrow down what changed across versions.