This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.
Week: 09 – 13 March 2026
Fedora Infrastructure
This team is taking care of day to day business regarding Fedora Infrastructure.
It’s responsible for services running in Fedora infrastructure.
Ticket tracker
CentOS Infra including CentOS CI
This team is taking care of day to day business regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It’s responsible for services running in CentOS Infratrusture and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker
Release Engineering
This team is taking care of day to day business regarding Fedora releases.
It’s responsible for releases, retirement process of packages and package builds.
Ticket tracker
RISC-V
This is the summary of the work done regarding the RISC-V architecture in Fedora.
- F44 rebuild will be slow until we clear the current queue in the build system (side note: until RISC-V enters primary Koji, it is likely to be out of sync with primary arch in terms of image delivery timelines). Engaged on ‘fedora-devel’ (and the Discussion forum) about primary vs. alternative arch requirements. Downstream needs brought the pending Fedora upstream work for LLVM and Java into the foreground. Reviewed the link-time optimization (LTO) situation in Fedora RISC-V: for now we’ll keep it disabled, the LTO gains are rather small, and it gives us much better build times. Evaluated migrating documentation from Wiki to Forge, but it remains a bit of a low-priority for now.
- Resolved a “unified kernel” (soon to be “omni kernel”) boot failure on P550
- Debugged a small regression in ‘arch-test’ reported on the RISC-V Matrix channel.
- Chip away at the RISC-V tracker
- Make progress on draining the queue on the tasks tracker
QE
This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.
- Fedora 44 Beta was approved last week and is getting released this week. This involved a lot of release validation tests, blocker bugs management, common issues writeup, and more.
- Ran Podman test week + I18N week (currently in progress). Article and blog invites were created for both events.
- Cooperation started with Desktop QA wrt adding fmf tests for mesa fedora CI.
- The Testdays Web app now has a unit tests suite.
Forgejo
This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.
- Many new orgs added to Forgejo, and migrations ramping up. Fixing migration issues on the fly
- Pagure static pages archive almost ready to be published for review
- Continued work on Private Issues:
- Implement issue-level access control (DB queries still outstanding)
- Fix hanging and failing tests, (partially caused by rebased upstream, not yet pushed)
- Switch from pointers to sql.NullInt64 types of public/private issue ID pairs for safety and better consistency with existing code
- RPM: Package 14.0.3
EPEL
This team is working on keeping Epel running and helping package things.
- Traveling back from Scale (Trip report will follow)
- Maintenance work (business as usual)
- WIP: matrix bot to look into forgejo repo
UX
This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project
If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.
Recent Comments