Previous weeks

  1. From March 23 to March 29

    A primary focus across many groups was the upcoming Fedora 44 release, with teams like Quality, KDE, and Server conducting blocker bug reviews, testing new features, and gathering user feedback, especially for the new Raspberry Pi 5 images. In parallel, planning for Fedora 45 is well underway, with FESCo and the broader community discussing and approving Change Proposals, most notably a breaking update to python-setuptools and enabling PAM support in chpasswd. A major, project-wide effort is the infrastructure migration from Pagure to Fedora Forge (Forgejo), a topic central to the Council, Infrastructure, and Releng teams who are managing the timeline, URL structures, and new CI workflows. Improving the user experience also emerged as a key theme, highlighted by a widespread discussion across the Quality, KDE, and Design teams in response to a new user's detailed feedback on the "broken and hostile" bug reporting workflow.

    read more

  2. From March 16 to March 22

    The primary focus across most groups this week was the upcoming Fedora 44 release, with a major emphasis on its Final Freeze. Teams including Quality, Server, ARM, and Workstation issued widespread calls for community testing of final validation builds to identify and resolve blocker bugs, with specific feedback being gathered for new Raspberry Pi 5 images. Alongside this immediate release work, a significant common theme was platform migration. The move from Pagure.io to the new Forgejo instance was a key topic for the Council and Packaging Committee, who are navigating technical blockers and planning the transition process, while the CoreOS and Atomic teams discussed their migration to the Konflux build system. Strategic planning was also prominent, with both the Council and FESCo refining a new "Technology Innovation Lifecycle Process" proposal, and FESCo making key decisions to filter Flatpaks on Atomic Desktops and restrict ptrace by default.

    read more

  3. From March 09 to March 15

    The primary focus across the Fedora Project this week was the Fedora 44 release cycle, culminating in the announcement and release of the Fedora 44 Beta. This involved a wide range of coordinated efforts, including final preparations and testing by the Releng, Infrastructure, and Quality teams, who held blocker review meetings to triage bugs and approve freeze exceptions. Several groups, including the Workstation, KDE, and ARM teams, were specifically involved in testing and announcing new F44 images for the Raspberry Pi 5. Beyond the immediate release, a common thread was discussion on future project direction and policy, with the Council and FESCo debating proposals like a "Technology Innovation Lifecycle" and new membership criteria. Other ongoing work included infrastructure improvements, such as migrations to Fedora Forge, and the introduction of new change proposals for the upcoming Fedora 45 release.

    read more

  4. From March 02 to March 08

    Across the project, many groups are working on the ongoing migration of repositories and documentation from Pagure to the new Forgejo instance. Several teams are also beginning to plan for the next release, with new change proposals for Fedora 45 being introduced for features like a DRM Panic Frontend and IPv6-mostly support. The focus of this week, however, was squarely on the Fedora Linux 44 Beta release. The Quality, Release Engineering, Infrastructure, and Server teams all coordinated their efforts around testing and validating the Beta release candidates, which culminated in a successful Go/No-Go meeting and the announcement of a public release scheduled for Tuesday, March 10th, 2026.

    read more

  5. From February 23 to March 01

    Across the project, many groups are focused on infrastructure migration and preparing for the next release. The most significant focus this week was the upcoming Fedora 44 Beta, with Release Engineering entering a freeze, the Quality and Server teams organizing testing and reviewing blockers, and FESCO deferring several incomplete changes to Fedora 45. A second major, cross-team effort is the ongoing migration of repositories and tickets to the new Forgejo instance, a task mentioned by the Infrastructure, Forgejo, UX, and AI teams, and underscored by the formal announcement of Pagure.io's decommissioning. Other common work includes routine package maintenance, highlighted by the KDE team managing the fallout from the recent Plasma 6.6 update and the EPEL team completing its mass branching for the next RHEL point release.

    read more

  6. From February 16 to February 22

    The primary focus this week was the Fedora 44 release cycle, which reached a significant milestone with the Beta freeze and code complete deadline. This prompted many groups, including FESCo, Quality, and various SIGs, to review change proposals, process blocker bugs, and prepare for the upcoming Beta release. A common thread across several teams, such as Mindshare, EPEL, and Design, was the ongoing migration of repositories and issue trackers to the new Forgejo instance. Additionally, package maintenance and cleanup were prominent activities, highlighted by the final push to retire the deprecated python-mock package, the retirement of several long-term failing packages, and a notable FESCo-initiated discussion about the responsibilities of package maintainers, particularly concerning the use of Bugzilla auto-responders.

    read more

  7. From February 09 to February 15

    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.

    read more

  8. From February 02 to February 08

    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.

    read more

  9. From January 26 to February 01

    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.

    read more
There is a draft, if you're curious 😉

links

social