On Wed, Mar 4, 2026, at 9:27 AM, Neal Gompa wrote: > On Wed, Mar 4, 2026 at 6:13 AM Michel Lind <[email protected]> wrote: > > > > On Tue, 2026-03-03 at 13:30 -0800, Neal Gompa wrote: > > > On Tue, Mar 3, 2026 at 12:45 PM Michael Catanzaro > > > <[email protected]> wrote: > > > > > > > > On Tue, Mar 3 2026 at 11:48:18 AM -08:00:00, Neal Gompa > > > > <[email protected]> wrote: > > > > > * ABRT UI needs a better flow for connecting to RHBZ > > > > > > > > Are we going to phase out Red Hat Bugzilla or not? I think yes, > > > > because > > > > Red Hat won't continue maintaining it forever, right? Let's focus > > > > effort on the future, not on functionality that soon won't matter. > > > > > > > > > > Okay, I'll generalize it then: connecting to Bugzilla. > > > > > Connecting to an issue tracker, more like? I think what Michael is > > getting at is that any effort to improving ABRT Bugzilla integration is > > wasted given it's a legacy platform. > > > > RHBZ might be a legacy platform, but I will still continue to advocate > that we should migrate to a new Fedora Bugzilla instance powered by > upstream Bugzilla. There are no other good options that are open > source, and at least Bugzilla has people who will take money for > improving things in the direction we want.
What 5 things should Fedora Infrastructure drop in order to make this happen. Bug tracking systems require a lot of specialized knowledge to keep running because of the many things you find below as needed. They need a DBA, regular maintenance and handholding to keep going, and a bunch of other things which would basically need to drop a lot of other services. At the moment, this is a zero to negative sum game. For every new neat thing people want, several things currently working mosat likely have to be EOL. > I really don't want to contemplate using Forgejo for bug tracking > because that would be extremely painful as a maintainer. Bugzilla has > rich query reports, structured data input modeling, and a useful API > for automation and lifecycling bugs. Not to mention it has nice things > like stable bug IDs regardless of component or ownership, global > reporter/assignment scope, and relationship modeling. > > And of course, there are lots of external and internal integrations > with Bugzilla that carrying over to a new instance would be > tremendously easier. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > -- > _______________________________________________ > devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://forge.fedoraproject.org/infra/tickets/issues/new > -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
