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... [2] https://forge.fedoraproject.org/fesco/rhbz-replacement-requirements [3] https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro... [4] https://www.youtube.com/watch?v=tQz5VDh9gkQ
Kindest regards, Aoife
On Tue, Aug 25, 2026 at 10:39 PM Aoife Moloney via devel < devel@lists.fedoraproject.org> wrote:
Hi all,
Following todays FESCo meeting[1], please be advised that the deadline to submit your bug tracker workflow(s) is September 1, 2026.
I might be the only one who was caught by surprise, but there was no deadline mention in the original call for action, and so we (Quality) did create a ticket [1] but didn't actually work on it yet. I lived under the assumption that there's plenty of time because the original email said "We will also separately reach out to individual groups and stakeholders in the project..." and nobody poked us yet, so there's still ample time, right? As I currently read it, there are only 3 working days to submit it (and since this Friday is a day off for Red Hat, just two actual business days). We'll still try to do our best, but... can the deadlines (at least their rough estimates) be communicated more in advance next time, please? So that we can prioritize better. Thanks.
[1] https://forge.fedoraproject.org/quality/tickets/issues/932
On Wed, Aug 26, 2026 at 4:18 PM Kamil Paral via devel devel@lists.fedoraproject.org wrote:
I might be the only one who was caught by surprise, but there was no deadline mention in the original call for action, and so we (Quality) did create a ticket [1] but didn't actually work on it yet. I lived under the assumption that there's plenty of time because the original email said "We will also separately reach out to individual groups and stakeholders in the project..." and nobody poked us yet, so there's still ample time, right? As I currently read it, there are only 3 working days to submit it (and since this Friday is a day off for Red Hat, just two actual business days). We'll still try to do our best, but... can the deadlines (at least their rough estimates) be communicated more in advance next time, please? So that we can prioritize better. Thanks.
Sorry about that, we dropped the ball on that "reaching out to groups" thing ... It would make sense to me to extend the deadline a bit to give you more time. I'll raise that on the fesco ticket.
Fabio
The deadline has been extended a week, as per the decision from the last FESCo meeting, so please do try to submit your workflow(s) to the repo before 7 September 2026.
On Wed, Aug 26, 2026 at 11:31 PM Fabio Valentini decathorpe@gmail.com wrote:
On Wed, Aug 26, 2026 at 4:18 PM Kamil Paral via devel devel@lists.fedoraproject.org wrote:
I might be the only one who was caught by surprise, but there was no
deadline mention in the original call for action, and so we (Quality) did create a ticket [1] but didn't actually work on it yet. I lived under the assumption that there's plenty of time because the original email said "We will also separately reach out to individual groups and stakeholders in the project..." and nobody poked us yet, so there's still ample time, right? As I currently read it, there are only 3 working days to submit it (and since this Friday is a day off for Red Hat, just two actual business days). We'll still try to do our best, but... can the deadlines (at least their rough estimates) be communicated more in advance next time, please? So that we can prioritize better. Thanks.
Sorry about that, we dropped the ball on that "reaching out to groups" thing ... It would make sense to me to extend the deadline a bit to give you more time. I'll raise that on the fesco ticket.
Fabio
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
-
Aoife Moloney -
Fabio Valentini -
Kamil Paral