Community Update – Week 17 2026 – Fedora Community Blog

This is a report created by CLE teamwhich is a team that contains community members working in various Fedora groups, for example Infrastructure, Release Engineering, Quality, etc. This team is also moving forward some initiatives within the Fedora project.

Week: 20 – 24 April 2026

Fedora Infrastructure

This team takes care of the day-to-day affairs regarding Fedora infrastructure.
It is responsible for services running in Fedora infrastructure.
Ticket tracker

CentOS Infra including CentOS CI

This team takes care of day-to-day matters regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It is responsible for services running in CentOS Infrastructure and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

Release Engineering

This team takes care of the day-to-day affairs regarding Fedora releases.
It is responsible for releases, package retirement process and package building.
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; to go through about 300 builds/day. (NB: This is still pretty decent, given the reduced builds we have. Fedora also has a non-trivial number of ‘noarch’ packages; they can be imported into RISC-V Koji without a rebuild.)
• Tried an upcoming server hardware called SpacemiT K3. I got 24 hour remote access (with some restrictions). Uploaded some basic data. Ran an initial benchmark for building ‘binutils’:
  • K3 is ~6.5x faster 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 host’s default compiler flags differ.)
• Started a thread with a few people about a backup plan to improve the reliability of builder hardware. Roughly: until server-grade hardware is widely accessible, see if we can get some of the current “workhorse” (SiFive P550), and make them available somewhere so they can be easily connected to RISC-V Koji.
• Conferences: RISC-V EU summit schedule preparation has been done.

FE

This team takes care of the quality of Fedora. Maintenance of CI, organization of test days
and keep an eye on the overall quality of Fedora releases.

Forgejo

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

• (Forgejo) Participated in the Fedora Forge Sprint Planning meeting call
• (Forgejo) Strategize the cooperation on the private issues feature inclusion
• (Forgejo) Private Issues, Web UI: Lists the private issues in its separate section (Follow-up A) (Follow-up B) (Follow-up C)
• (Forgejo) Private Issues, Web UI: Show the contents of the private issue ticket (Follow-up A) (Follow-up B) (Follow-up 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 beneficiary 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: Print the basic private issues frontend codebase implementation (Triaged) (Succeed)
• (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) Fundamental private issues frontend codebase implementation (opened)(Succeed)

APPLE

This team is working to last Apple running and helping pack 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 of FTI bugs

List of new releases of applications 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 at matrix.