To this end, I’ve enlisted the help of the Don Zickus, kernel
developer extrordinaire, and Adam Williamson, the inimitable
Fedora QA guru. The plan is to create a set of user tests for the
most common bluetooth tasks. This plan has several goals.
First, we’d like to know when stuff is broken. For example, the recent
breakage in linux-firmware. Catching this stuff early is a
Second, we’d like to get high quality bug reports. When things do break, vague
bug reports often cause things to sit in limbo for a while. Making sure we have
all the debugging information up front can make reports actionable.
Third, we’d (eventually) like to block a new Fedora release if major
functionality is broken. We’re obviously not ready for this step yet. But once
the majority of workflows work on the hardware we care about, we need to ensure
that we don’t ship a Fedora release with broken code.
To this end we are targeting three workflows which cover the most common cases:
For more information, or to help develop the user testing, see the Fedora
QA bug. Here’s to a better future!