Hi all,
Following todays FESCo meeting[1], please be advised that the deadline
to submit your bug tracker workflow(s) is September 1, 2026. You can
submit your workflow(s) in the requirements repo[2]. This has been
previously announced [3], and the collection of the workflows has
begun a larger effort to identify the best application to replace rhbz
(Red Hat Bugzilla), which Fedora currently uses. While there is no
confirmed sunsetting date for our current Bugzilla, we expect
maintenance to be significantly reduced by the end of this year[4]. To
prepare for this, we are collecting impacted workflows, and setting
some baseline requirements to investigate the viability of either an
upstream instance of bugzilla, or incorporating our bugf tracking
needs into Fedora Forge. Either choice will require significant
effort, but first, we need to understand our Project's critical or
core bug tracker requirements to make the most informed choice.
If you are collecting your workflow elsewhere, please either open a
ticket in the tracker and link to it there, or send me the link
directly and I will include it in the repo.
[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-…
[2] https://forge.fedoraproject.org/fesco/rhbz-replacement-requirements
[3] https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
[4] https://www.youtube.com/watch?v=tQz5VDh9gkQ
Kindest regards,
Aoife
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
In accordance with FESCo's Inactive Packager Policy[1], packagers that
have been identified
as inactive have a ticket in the find-inactive-packagers repo[2]. One
week after the final
release, packagers who remain inactive will be removed from the packager
group. (Note that
pagure.io is one of the systems checked for activity, so commenting on
your ticket that you're
still around will prevent you from showing up in the second round.)
If you have suggestions for improvement, look for the open feature
issues[3] and file an issue
in the find-inactive-packagers repo[4] if it's not there already.
For the curious, here are the stats from today's run:
### Found 1391 users in the packager group. ###
### Found 557 users with no builds in Koji over the last year. ###
### Found 481 users with no activity in forge.fedoraproject.org in the
last year. ###
### Found 369 users with no activity in src.fp.org over the last year. ###
### Found 353 users which didn't post any message in Fedora Discussion
over the last year. ###
### Found 322 users which also show no activity in Bodhi over the last
year. ###
### Found 302 users which also show no activity in mailing lists over
the last year. ###
### Found 226 users which also show no activity in Bugzilla over the
last year. ###
[1]
https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
[2]
https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?q=…
[3]
https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues?q=…
[4]
https://forge.fedoraproject.org/packaging/find-inactive-packagers/issues/new
pagure.io has transitioned to a permanent read-only static archive. All
public projects, issues, and pull requests remain accessible on pagure.io
for historical reference.
Forge (forge.fedoraproject.org) is now the primary platform for Fedora
project development. Fedora project-related repositories been migrated by
their owners to Fedora Forge . Non-Fedora related repositories may have
moved to other platform including Codeberg, GitLab, and GitHub.
Git repositories remain accessible read-only via HTTPS, allowing you to
clone or migrate individual repositories to new locations if needed.
Note: pagure.io no longer supports login, API access, or any modifications.
For new projects or to contribute to Fedora, visit
https://forge.fedoraproject.org
For questions or issues, visit https://forge.fedoraproject.org/infra/tickets
Hi Fedora folks! 👋🏻
Software Freedom Conservancy (SFC) honored *Mark J. Wielaard* (mjw) with
the second annual Distinguished Service Award in Software Freedom at *FOSSY
2026*. This award recognizes decades of dedicated service to software
freedom in both volunteer and professional capacities.
Within Fedora, Mark plays a critical role in maintaining the foundation of
our development and debugging stack. He is the package maintainer for
several core packages, including:
* debugedit
* dwz
* elfutils
* rpm
* systemtap
* valgrind
Beyond his essential packaging work for Fedora, Mark's broader impact on
the FOSS ecosystem includes:
* *Tooling & Standards*: Long-time maintainer of the Valgrind and elfutils
projects, and member of the DWARF Debugging Standard Committee.
* *Securing Open Java*: Led the IcedTea project to bridge core Java
libraries with free software alternatives.
* *Critical Infrastructure*: Voluntarily maintaining Sourceware, a
developer hosting platform.
Please join in congratulating Mark on this outstanding and deeply deserved
recognition! 👏🏻🎉👏🏻
You can read the full SFC announcement and celebration remarks here:
https://sfconservancy.org/news/2026/aug/12/mark-j-wielaard-receives-2-annua…
--
*Justin Wheeler* (*he/him*) || 📧 jwheel(a)redhat.com || 🔗 jwheel.org
*Formerly Justin W. Flory*
*AI Alignment* Community Architect, *Fedora*
TZ=America/Atlanta (UTC-4) 🕗
*Fedora is a registered Digital Public Good
<https://app.digitalpublicgoods.net/a/12003>*
While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
Planned Outage - updates/upgrades/reboots - 2026-08-20 20:00 UTC
There will be an outage starting at 2026-08-20 20:00 UTC,
which will last approximately 6 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2026-08-20 20:00 UTC'
Reason for outage:
We will be applying updates all around and rebooting servers. In addition, we will be migrating some instances to rhel10.
Services will be up and down during the outage window as specific servers are upgraded, rebooted or reinstalled.
Affected Services:
Most non user facing services will be affected for limited times during the outage window.
Ticket Link:
https://forge.fedoraproject.org/infra/tickets/issue/13500
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
or add comments to this ticket for more information or feedback.
Updated status for this outage may be available at
https://www.fedorastatus.org/
Hello all,
Fedora 45 branched off Rawhide today, 2026-08-11.
Please be sure to do a `git fetch -v` to pick up the new branch.
As an additional reminder, Rawhide and Fedora 45 are completely isolated
from previous releases. Therefore, any changes made for F45 must also be
applied to the Rawhide branches.
Note that until we have a successful compose of F45, we will be in a
post-branch freeze [1]. Once complete, the compose will appear here [2].
Automatic update creation is currently enabled for both Fedora 45 and
Rawhide, meaning builds will automatically receive a Bodhi update without
any manual action required. At the start of Beta Freeze (2026-08-25 as per
the Fedora 45 release schedule [3]), the updates-testing repository will be
enabled and manual Bodhi update submissions will be required, as is the
case for all stable releases.
Additionally, some package updates were unpushed during Mass Branching to
prevent an inconsistent state.
Discussions are happening in the Release Engineering Matrix room [4] and in
the Mass Branching tracker ticket [5] if you have any questions or concerns.
Best regards,
Patrik Polakovic
Fedora Release Engineering
[1]
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#post-branch-free…
[2] https://dl.fedoraproject.org/pub/fedora/linux/development/45/
[3] https://fedorapeople.org/groups/schedule/f-45/f-45-releng-tasks.html
[4] https://matrix.to/#/#releng:fedoraproject.org
[5] https://forge.fedoraproject.org/releng/tickets/issues/13451