While Fedora 45 has not yet been released, the underlying infrastructure governing its development remains a sophisticated architecture of automated builds and rigorous testing. The process begins at src.fedoraproject.org, where every package's source definitions are stored in individual Git repositories. These repositories contain RPM spec files, downstream patches, and source files pointing to upstream tarballs kept in a separate lookaside cache, ensuring that large binary files do not clutter the Git workspace.
Packagers interact with these repositories primarily through fedpkg, which generates a URL for specific commits and passes it to Koji. Koji acts as the backbone of Fedora’s build system—a hub-and-spoke architecture in use since Fedora 7. It operates using a passive XML-RPC server fronting a PostgreSQL database, where builder daemons poll for work and create a fresh Mock chroot for every build to ensure a clean-room environment.
The system organizes builds into tags—named collections that support multiple inheritance. These tags map specific build targets to destinations, with the 'rawhide' branch serving as the rolling development area while branches like 'f44' correspond to stable releases. The infrastructure currently utilizes a mix of Pagure and Forgejo for hosting during an ongoing migration.
To ensure reliability, Koji builds are passed through Bodhi for branched releases. Bodhi acts as a gatekeeper, moving updates through pending, testing, and stable phases based on karma (positive or negative feedback from users and automated tests). While most updates need 7 days of testing or sufficient karma to reach 'stable,' critical path packages face stricter requirements, such as 14 days in the testing phase. Bodhi also integrates with Greenwave and ResultsDB for continuous integration gating.
Once a package passes these gates, downstream orchestration begins via Pungi—a name derived from the snake-charming instrument. Pungi manages 'composes' (triggered by cron for nightly Rawhide builds or manually for milestones) by reading configurations from the pungi-fedora repository. During the Pkgset phase, it creates an auditable snapshot of the package set based on a Koji tag.
The creation of final products is guided by 'fedora-comps' and variant files (such as those for Workstation or Silverblue). The process concludes with two critical phases: Buildinstall, where Lorax creates a base boot.iso by configuring a minimal set of packages; and Createiso, which uses xorriso to overlay the full package set and metadata onto that foundation to produce the final installer ISOs.