arm September 2026

arm@lists.fedoraproject.org

4 participants
6 discussions

2026-09-28 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 27 Sep '26

27 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-28 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2026-09-21 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 20 Sep '26

20 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-21 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 6 proposed blockers and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Collection of this group's data for a LLM-powered weekly report
by Aurelien Bompard 17 Sep '26

17 Sep '26

Hi folks, I'm generating a weekly report of activity in the Fedora project centered on teams and SIGs, it's called "This Week in Fedora" <https://abompard.fedorapeople.org/twif/>. This generation uses an LLM. The goal is to make it easier to catch up with everything that's going on in the project, and to give visibility to each group's work and requests for help or testing. I think that from a newcomer's point of view, having an insight on what a group is working on at a point in time is helpful to decide whether it's interesting and worth contributing to. I'm collecting activity from: - this mailing-list - discourse posts with the `#arm-sig` tag - meetings in Matrix meeting channels, but I haven't seen any for this team recently In the latest version, I've added the possiblity to gather messages exchanged in Matrix channels. The `#arm` channel is public and its history is available to anyone, but a quite a few people in mutiple Matrix channels were unhappy about the LLM collecting this info, for various reasons. I would like to know whether this group is OK with my program collecting and submitting info to an LLM from the following sources: 1. mailing-lists, discourse posts and meetings (if any) 2. a ticket tracker in the ARM group on Fedora Forge, if you end up creating one in the future 3. the matrix channel I would like to make the case for source 3 (the Matrix channel) because I think it's less obvious: knowing the "tone" of a conversation and the currently discussed subjects before joining is very important to help contribute to it. It's like when you're added to an empty group chat and you don't know how to start. That's why we show history to new channel members, and this would be the same idea at a higher level. Plus there's actual work going on in there for a lot of groups. That said, I recognize that the form of the tool influences its use, chat messages are usually less thought-through than emails or forum posts, and members could be indimidated that something they write there and regret end up in a visible summary (the program respects message edits, but anyway). Since my goal is to foster participation, the one thing I don't want to do is to hinder it in another way. I know I've asked this in the chat last week but someone in another room noted that people can easily miss Matrix messages, which it true. Please decide which collected sources, if any, you are OK with (and if you work in other places that you would like to have collected, of course (I can do RSS feeds!)). If the group is OK with Matrix channel collection but some individuals aren't, I can also exclude certain Matrix usernames from collection throughout the Matrix channels that are not meetings. I'm happy to answer questions if you have any. Thanks!

1 0

Latest brcmfmac breaks RPI5 wifi
by David Legg 14 Sep '26

14 Sep '26

Anybody interested in the details? Not sure exactly which of these updates does it: :D # !dnf dnf distro-sync Updating and loading repositories: Repositories loaded. Package Arch Version Repository Size Upgrading: brcmfmac-firmware noarch 0:20260910-1.fc45 updates-testing 9.5 MiB replacing brcmfmac-firmware noarch 0:20260810-1.fc45 fedora 9.5 MiB iwlwifi-mld-firmware noarch 0:20260910-1.fc45 updates-testing 23.4 MiB replacing iwlwifi-mld-firmware noarch 0:20260810-1.fc45 fedora 20.2 MiB iwlwifi-mvm-firmware noarch 0:20260910-1.fc45 updates-testing 62.7 MiB replacing iwlwifi-mvm-firmware noarch 0:20260810-1.fc45 fedora 62.7 MiB linux-firmware noarch 0:20260910-1.fc45 updates-testing 48.7 MiB replacing linux-firmware noarch 0:20260810-1.fc45 fedora 50.0 MiB linux-firmware-whence noarch 0:20260910-1.fc45 updates-testing 462.2 KiB replacing linux-firmware-whence noarch 0:20260810-1.fc45 fedora 449.3 KiB realtek-firmware noarch 0:20260910-1.fc45 updates-testing 6.9 MiB replacing realtek-firmware noarch 0:20260810-1.fc45 fedora 6.9 MiB

2 11

2026-09-14 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 13 Sep '26

13 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-14 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 1 proposed blocker and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2026-09-07 @ 16:00 UTC - Fedora 45 Blocker Review Meeting
by Adam Williamson 06 Sep '26

06 Sep '26

# F45 Blocker Review meeting # Date: 2026-09-07 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 2 proposed blockers and 7 proposed freeze exceptions for Beta. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker… The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day! I may not see you tomorrow as I'll be on vacation, but somebody will be there to run the meeting. [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2026