The meeting logs are available here: https://meetbot-raw.fedoraproject.org/teams/quality/quality.2025-08-18-15.01.html https://meetbot-raw.fedoraproject.org/teams/quality/quality.2025-08-18-15.01.log.html
Also, let’s try something new today! Here’s an AI-generated meeting summary. Tell me if you think it’s useful or not. ~~~~~~~~ Here is an AI-generated summary of a Fedora Quality meeting [1] from 2025-08-18. Please be aware that the summary is intended for a quick convenient recapitulation of the meeting, but might contain factual errors. Read the full meeting log for all the details. #### Previous meeting follow-up There were no follow-up items from the previous meeting. #### Fedora 43 status Fedora 43 is now Branched. The team has branched successfully, and the focus will now shift to addressing blocker bugs. Community members are encouraged to vote on proposed blocker bugs for the Beta [2] and Final [3] releases, in accordance with the Fedora Release Criteria [4]. Blocker meetings for bugs not resolved through voting will begin soon. Community members can also contribute by testing and completing release validation matrices. Test coverage can be viewed on the OpenQA testcase stats page [5]. A noteworthy problem was raised by Derek Enz, who reported that the aarch64 KDE image is failing to boot on the Raspberry Pi 4. Kamil Páral asked him to file a bug report and propose it as a blocker, which he agreed to do. Lukáš Růžička, who has been running Fedora 43 since the previous day, noted that he has not encountered any serious issues. #### Scope reduction discussion The ongoing discussion on reducing the scope of the Quality team's work was reviewed, with a summary available on the Fedora Discussion forum [6]. Three proposals have already been implemented: * Dropping the optical media boot release criterion. * Dropping the Intel-based Macbook dual boot release criterion. * Requiring just the standard set of applications to be release-blocking on Workstation x86\_64, not all of them. Other proposals are more complex and require further discussion and possible tweaks. These include reducing BIOS support (with a likely exception for RAID on Server), removing release-blocking status for aarch64 desktops (which has met strong opposition from the KDE SIG), de-editioning IoT, and unifying aarch64 hardware support (which has received pushback). Derek stated that he and another member of the KDE SIG are covering aarch64 testing. Kamil acknowledged the KDE SIG's valuable work. Since Neal from the KDE SIG has stated they will handle the testing, the Quality team will likely only pursue dropping GNOME on aarch64 as a release-blocker for now. #### Test Day / community event status All scheduled Test Days have finished. Due to staffing issues, no further events are planned, and the team no longer has a person dedicated to proactive organization. The Quality team is asking other teams and community members to contact them by creating a ticket if they wish to run a Test Day. More information can be found on the QA/Test Days wiki page [7]. Hristo Marinov asked if it was mandatory to be part of a SIG to organize a test day, and was told that any community member can do so. He expressed interest in organizing a Test Day for Fedora Atomic Desktops and confirmed he already has an agreement with the maintainer. Kamil encouraged him to create a ticket to discuss the details. #### Open floor No other major topics were discussed, and the meeting was concluded. [1] https://fedoraproject.org/wiki/QA/Meetings [2] https://qa.fedoraproject.org/blockerbugs/milestone/43/beta/buglist [3] https://qa.fedoraproject.org/blockerbugs/milestone/43/final/buglist [4] https://fedoraproject.org/wiki/Fedora_Release_Criteria [5] https://openqa.fedoraproject.org/testcase_stats/43/ [6] https://discussion.fedoraproject.org/t/fedora-quality-scope-reduction-announcement-and-summary/160523 [7] https://fedoraproject.org/wiki/QA/Test_Days
-- _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
