The future of Bugzilla Part 2 - 2026-07-29 @RedHatOpen
The future of Bugzilla Part 2 - 2026-07-29  @RedHatOpen
Uploaded August 2026 | Updated September 2026, 1 hour ago
The future of Bugzilla Part 2

This is an auto-generated summary of the FRCL call on 2026-07-29:

Retirement of Bugzilla was discussed with exploration of replacement platforms and alignment on formal requirements gathering.

Bugzilla Retirement Outlook
Retirement of the Bugzilla instance is planned for the coming year as most teams have migrated. The primary concern is preserving access to legacy data for users.

Evaluating Replacement Platforms
Current replacement options like Forjo lack critical features necessary to support existing workflows. Discussants emphasized that shifting systems without a thorough requirements gathering process risks operational failure.

Governance and Process Strategy
The Fedora Engineering Steering Committee and Fedora Council will lead the platform selection effort. The group decided to prioritize analyzing historical data and internal needs over broad community surveys.

Jira Epic: redhat.atlassian.net/browse/FRCL-58
Gemini AI Summary: docs.google.com/document/d/1w2YhH_9CQwH3GcB7GaN8dUDGjpWwUjtlYJAJoBrv_7s/edit?usp=meet_tnfm_calendar
The future of Bugzilla Part 2 - 2026-07-29Containers in cars - Container Plumbing Days 2023Upstream: Open Source Origin StoriesCommunity coordination for embargoed security updates - 2026-01-21Open Source and Business ModelsSecure Container Supply Chains DiscussionRed Hat NEXT! 2022: The Evolution of ComputePost-Flock 2026 Roundup - 2026-06-24Community Central: Performance Co-PilotUpstream: A Conversation about the Foreman ProjectCommunity Central: Intro to Ceph: Open Source Distributed Storagellm-d 101: Why Do We Need It?
Red Hat Open |

The future of Bugzilla Part 2 - 2026-07-29

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER