I hope not, but it’s possible unfortunately. Ideally we’d be able to automate the required testing for that; the most obvious problem there is automating testing of screen reading functionality. openQA has a kinda clever feature for doing audio testing where it records a waveform and then runs its image comparison stuff on the waveform image, but I have never tried really using that feature in anger before, I don’t know whether it’s robust enough to reliably back an entire audio-based workflow. If we can’t find a way to automate that it’d be a significant chunk of manual testing, and we’d have to figure out some way to handle that.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| 🪦 Proposal: Re-consider Edition status for IoT | 39 | 1247 | September 9, 2025 | |
| ❌ Proposal: No longer block releases on ARM desktop | 45 | 1240 | September 2, 2025 | |
| Fedora-Council/tickets ticket #504: Request to upgrade Fedora KDE Desktop Spin to Edition status under the Personal Systems WG | 39 | 3580 | November 9, 2024 | |
| 2025-08-18 @ 15:00 UTC - Fedora Quality Meeting | 1 | 79 | August 19, 2025 | |
| F41 Change Proposal: Mark Fedora KDE AArch64 as Release-Blocking (System-Wide) | 19 | 763 | July 20, 2024 |