Here is an AI-generated summary of a Fedora Quality meeting from 2025-11-10.
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
Adam Williamson confirmed there were no action items from the previous meeting.
Fedora 44 status
The team discussed the current state of Fedora 44 (Rawhide).
Adam noted he hadn’t seen any major “breakage” headlines during his vacation.
Kamil Páral agreed, stating he hadn’t seen any “fires”.
Lukáš Růžička, who had been monitoring updates, reported they were “mostly good”.
The consensus was that F44 seems to be in a reasonable state.
Test Day / community event status
Kamil delegated this topic to Petr Sklenar, who is a new addition to the team.
Petr is organizing the upcoming FreeIPA-WebUI Test Day, scheduled for 2025-12-02. He is currently in touch with developers to add their test cases to the wiki page.
A request for a PyTorch Test Day has also been received.
Petr reported he lacked permissions to create the event on the Fedora Calendar. Kamil identified this was tied to FAS group membership and added Petr to the qa-admin group to resolve the issue.
Forgejo migration
The team discussed the ongoing migration from Pagure to Forgejo.
Kamil noted that a blocking issue for migration has been closed.
The plan is to first experiment on the staging instance (forge.stg.fedoraproject.org) before migrating production projects.
Lukáš Růžička volunteered to test the migration by moving fedora-easy-karma (FEK) to the staging instance. The migration is handled by a UI button and is expected to preserve issue numbers.
Several users (Kamil, Petr) experienced login issues with the staging instance. Adam suggested this might be due to the staging FAS server using an older password database. humaton (jednorozec) joined the channel to help debug the authentication failures.
During the discussion, Lukáš successfully completed the test migration of FEK to staging and reported that, “On first sight, it looks good”.
policy: updates-testing policy exceptions
Kamil brought up a QA ticket regarding the updates-testing policy.
The Issue: Podman developers would like to keep their Release Candidate (RC) builds permanently in the updates-testing repository to gather more testing, and only push the final version to stable. This conflicts with the current policy, which states that updates in updates-testing must be intended for stable release.
Discussion:
Kamil clarified that QA cannot grant an exception but can provide an opinion to FESCo (Fedora Engineering Steering Committee).
Adam expressed that he doesn’t “love it” because it “muddies the purpose” of the repository.
Kashyap Chamarthy agreed, worrying podman would become a “unique snow flake”.
Kamil stated he does not want a list of exceptions; if this is a good idea, FESCo should be asked to clarify the policy for everyone.
Lukáš raised concerns that if all packages were allowed to do this, it would increase the QA workload checking failed tests. He also suggested alternative testing methods could be used, though Kamil noted the developers feel updates-testing provides the best impact.
Outcome: No firm decision was made, but the general sentiment was hesitant.
actionable: Action items
Kamil Páral will update the policy ticket with a summary of the team’s discussion.
Previous meeting follow-up
Fedora 44 status
Test Day / community event status
Forgejo migration