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: 20 – 24 April 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

• [Badges/Outreachy] refactor: Extract duplicated search dropdowns and error handling into reusable components [Suggested]
• [Badges/Outreachy] Refactor: Replace hardcoded email domain with config variable [Approved] [Resolved]
• [Badges/Outreachy] cleanup: remove dead template infrastructure from app.py [Suggested]
• [Badges/Outreachy] fix: add missing session.commit() in opt_out [Approved]
• [Badges/Outreachy] Add get_persons_by_nickname with pagination to TahrirDatabase [Rejected]
• [Badges/Outreachy] Readme.md file update [Suggested]
• disk auto-decryption problem on vmhost-x86-copr04
• Zabbix item to monitor LetsEncrypt certs on-disk

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

• Work through issues with new CS pungi builder.
• Remove buildsys10s-release repo from isa10s-packages-riscv-el10s-build
• Replace infra external (private) mirror for new machines deployment
• Migrate CI artifacts storage solution to el10

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

• Fedora 44 Final release preparation

RISC-V

This is the summary of the work done regarding the RISC-V architecture in Fedora.

• F44 rebuild: we’re halfway through; getting through about 300 builds/day.   (NB: This is still pretty decent, given the reduced builders we have.  Fedora also has a non-trivial number of ‘noarch’ packages; they can get imported into RISC-V Koji without a rebuild.)
• Tried out an upcoming server hardware called  SpacemiT K3.  I got 24h remote access (with some limitations). Uploaded some basic data. Ran an initial benchmark of building ‘binutils’:
  • K3 is ~6.5x faster at compiling ‘binutils’ compared to our current build horse P550. (NB: this is not a 100% apples-to-apples comparison, as P550 is on Fedora, while the K3 is on some FrankenLinux, so the default compiler flags from the host differ.)
• Started a thread with a few folks on a backup plan to improve reliability of builder hardware. Roughly: until server-grade hardware is widely accessible, see if we can get a few of the current “workhorse” (SiFive P550), and make them available somewhere so that they can be easily hooked to RISC-V Koji.
• Conferences: RISC-V EU Summit schedule preparation is done.

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.

• Extended openQA test coverage: notifications test running on updates (not just composes), new screen recording test, new partial kickstart install test
• Rmdepcheck (replacement for rpmdeplint repoclosure) improvements: swapped out the core implementation from XML parsing to clever dnf commands to make it simpler, more robust, faster, and work properly on EPEL packages/updates

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

• [Forgejo] Participated in the Fedora Forge Sprint Planning meeting call
• [Forgejo] Strategized the collaboration on the private issues feature inclusion
• [Forgejo] Private Issues, Web UI: List the private issues in its separate section [Followup A] [Followup B] [Followup C]
• [Forgejo] Private Issues, Web UI: Show the private issue ticket contents [Followup A] [Followup B] [Followup C]
• [Forgejo] Private Issues, Web UI: Investigate and implement the milestone changes on a private issue [Triaged]
• [Forgejo] Private Issues, Web UI: Investigate and implement the project changes on a private issue [Triaged]
• [Forgejo] Private Issues, Web UI: Investigate and implement the assignee changes on a private issue [Triaged]
• [Forgejo] Private Issues, Web UI: Investigate and implement the dependency changes on a private issue [Triaged]
• [Forgejo] Private Issues, Web UI: Push the foundational private issues frontend codebase implementation [Triaged] [Followup]
• [Forgejo] Private Issues, Web UI: Investigate and implement the content changes on a private issue [Triaged]
• [Forgejo] Private Issues, Web UI: Investigate and implement the content changes on a private issue [Triaged]
• [Forgejo] Foundational private issues frontend codebase implementation [Opened][Followup]

EPEL

This team is working on keeping Epel running and helping package things.

• Updated EPEL minor EOL SOP, to be used next month during the retirement of EPEL 10.1
• Routine packaging work, including CVE work and filing FTI bugs

List of new releases of apps maintained by I&R Team

COPR 2026-04-16 – Highlights

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.