Fedora ARM Release Changes Due To Red Hat QA Team Reduction
([Fedora] 2 Hours Ago
Fedora ARM)
- Reference: 0001573740
- News link: https://www.phoronix.com/news/Fedora-ARM-Changes-Red-Hat-QA
- Source link:
Due to a "significant portion" of Red Hat's internal QA team responsible for Fedora QA leaving the company or switching to other teams at Red Hat, there are some Fedora ARM release changes coming to deal with the reduced abilities of their quality assurance team.
Back in July was the [1]announcement of the Fedora Quality/QA team needing to reduce its scope of operations due to a number of those on Red Hat's internal team leaving the company or switching teams. In particular, some switching to work on AI projects or other tasks rather than QA. With fewer hands on that internal team, some of the Fedora ARM release criteria are changing slightly.
There was recently a [2]request to drop the release-blocking status for Fedora's ARM desktop spins due to the QA shortage. They felt the amount of QA time was inappropriate relative to the amount of ARM desktop use out there so Fedora Workstation AArch64 and Fedora KDE AArch64 images would no longer hold up a release.
At today's Fedora Engineering and Steering Committee (FESCo) meeting it was decided to leave AArch64 as release-blocking both for Fedora Workstation and Fedora KDE. But that's on the condition that blocking issues are maintained by Jeremy Linton for Fedora Workstation and then KDE Special Interest Group (KDE SIG) for Fedora KDE AArch64 issues. The formal Red Hat Fedora Quality/QA team won't be devoting resources so it's up to those interested to volunteer and maintain it to keep it release-blocking.
The other part of the scope reduction around Fedora ARM is the [3]FESCo request for guidance on supported ARM hardware. Basically to narrow down the list of supported ARM hardware targets to require less QA/testing for what is to be considered officially supported.
At the FESCo meeting today it was decided to get rid of a dedicated hardware compatibility list and to evaluate issues on a case-by-case basis for deciding if they are release blocking, similar to how Fedora x86_64 hardware issues are typically treated.
Aside from working to reduce the Fedora ARM burden on the Red Hat engineers working on QA, the smaller team is also behind the effort for [4]dropping CD/DVD optical media release criteria , no longer making Intel-based MacBook dual boot support release-blocking, and reducing the scope of BIOS-based (non-UEFI) systems. There has also been discussions on whether Fedora IoT Edition still makes sense and other areas where they can cutback their quality/testing resources.
[1] https://discussion.fedoraproject.org/t/fedora-quality-scope-reduction-announcement-and-summary/160523
[2] https://www.pagure.io/fesco/issue/3467
[3] https://www.pagure.io/fesco/issue/3466
[4] https://www.phoronix.com/news/Fedora-Release-Criteria-CD-DVDs
Back in July was the [1]announcement of the Fedora Quality/QA team needing to reduce its scope of operations due to a number of those on Red Hat's internal team leaving the company or switching teams. In particular, some switching to work on AI projects or other tasks rather than QA. With fewer hands on that internal team, some of the Fedora ARM release criteria are changing slightly.
There was recently a [2]request to drop the release-blocking status for Fedora's ARM desktop spins due to the QA shortage. They felt the amount of QA time was inappropriate relative to the amount of ARM desktop use out there so Fedora Workstation AArch64 and Fedora KDE AArch64 images would no longer hold up a release.
At today's Fedora Engineering and Steering Committee (FESCo) meeting it was decided to leave AArch64 as release-blocking both for Fedora Workstation and Fedora KDE. But that's on the condition that blocking issues are maintained by Jeremy Linton for Fedora Workstation and then KDE Special Interest Group (KDE SIG) for Fedora KDE AArch64 issues. The formal Red Hat Fedora Quality/QA team won't be devoting resources so it's up to those interested to volunteer and maintain it to keep it release-blocking.
The other part of the scope reduction around Fedora ARM is the [3]FESCo request for guidance on supported ARM hardware. Basically to narrow down the list of supported ARM hardware targets to require less QA/testing for what is to be considered officially supported.
At the FESCo meeting today it was decided to get rid of a dedicated hardware compatibility list and to evaluate issues on a case-by-case basis for deciding if they are release blocking, similar to how Fedora x86_64 hardware issues are typically treated.
Aside from working to reduce the Fedora ARM burden on the Red Hat engineers working on QA, the smaller team is also behind the effort for [4]dropping CD/DVD optical media release criteria , no longer making Intel-based MacBook dual boot support release-blocking, and reducing the scope of BIOS-based (non-UEFI) systems. There has also been discussions on whether Fedora IoT Edition still makes sense and other areas where they can cutback their quality/testing resources.
[1] https://discussion.fedoraproject.org/t/fedora-quality-scope-reduction-announcement-and-summary/160523
[2] https://www.pagure.io/fesco/issue/3467
[3] https://www.pagure.io/fesco/issue/3466
[4] https://www.phoronix.com/news/Fedora-Release-Criteria-CD-DVDs
minedot