The primary focus across many groups this week was the upcoming Fedora 44 Beta freeze. Teams were busy finalizing changes, preparing for the code completion deadline, and scheduling blocker review meetings to address release-critical issues. Alongside this release work, a major ongoing effort is the migration of infrastructure and issue trackers from Pagure to the new Forge/Forgejo platform, a topic of significant discussion for the Council, Infrastructure, and EPEL teams. Package lifecycle management was another common theme, with proposals to deprecate unmaintained packages like python-dateutil, efforts to retire packages that consistently fail to build, and work to finalize the removal of python-mock. Finally, the week marked a key milestone with the completed transition to Packit as the default CI for Fedora dist-git.

Many groups are coordinating efforts for the upcoming Fedora 44 release, with discussions centered on branching, mass rebuilds, and Change Proposals. A significant cross-team effort is the ongoing migration from Pagure to the new Forgejo instance, impacting infrastructure, release engineering, quality assurance, and steering committees, all of whom are planning and executing the move for their respective repositories and documentation. Additionally, there is a focus on updating key software stacks and policies, including NodeJS, MariaDB, and considering new security defaults like restricting ptrace.

Across the Fedora Project, multiple groups are heavily focused on preparing for the upcoming Fedora 44 (F44) release. A significant amount of work is dedicated to the mass branching event, with teams like Releng, Infrastructure, and Quality coordinating efforts, testing changes, and fixing build failures that have been exposed by mass rebuilds. Another major cross-team effort is the migration from Pagure to the new Forgejo platform (Forge). The Docs, Quality, and Infrastructure teams are all actively moving repositories, tickets, and documentation, as well as adapting their workflows and tooling to the new system. Finally, with the Flock conference's Call for Proposals deadline approaching, several groups, including CoreOS, Server, and the Atomic Initiative, are planning and discussing potential talks and Birds of a Feather (BoF) sessions to submit.

Across the Fedora Project, several common themes emerged this week. A major focus was the ongoing migration from Pagure to the new Forgejo platform, with the Infrastructure, Releng, Quality, and Packaging Committee groups all actively discussing the technical migration, adapting their workflows, and updating tooling. Preparation for the upcoming Fedora 44 release was another key activity, involving mass rebuilds, change proposal submissions, release testing, and planning for the mass branching event. Finally, the upcoming FOSDEM 2026 conference is having a significant impact, influencing meeting schedules, reducing team capacity, and serving as a key venue for community presentations and engagement.

Across the project, groups focused heavily on preparing for the upcoming Fedora 44 release, with the Release Engineering and Quality teams managing the mass rebuild while other SIGs worked to fix package build failures and submit change proposals. Another major cross-team effort was the ongoing migration of infrastructure from Pagure to the new Forgejo instance, impacting ticket trackers and code repositories for the Infrastructure, EPEL, Docs, and Quality teams. Many groups also dedicated time to planning for upcoming events, including FOSDEM, CentOS Connect, SCaLE, and the Fedora Council Strategy Summit, which influenced meeting schedules and work priorities.