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 main Amiga Imager repository is not public yet, but the underlying AmigaDiskKit GitHub repository is available now.
For now, send reproducible bugs, regressions, and release feedback by email. A public issue tracker for Amiga Imager itself can be added later once the main repository is opened.
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.