Discussed this in the KDE SIG meeting today. @rdieter will re-verify that our DrKonqi setup is working correctly for directing users to file bugs upstream with KDE. Additionally, we're going to periodically take a look at ABRT crash bugs in RHBZ and forward bugs to KDE Bugzilla as appropriate.

Also, we will need to talk to DrKonqi developers to see if Fedora's ABRT remote retrace infrastructure can be plugged into DrKonqi so that crash reporting can always include high quality backtraces.

Is there a way to list all ABRT crash bugs?

One thing that came up this time around: there's a number of blocker bugs, and @adamwill did a lot of diagnostic work and filed upstream bugs, but did not note upstream that these are blockers — which I totally understand, because it's obnoxious for users or downstreams to try to make their problems the developer's problem or responsibility.

But, I think KDE devs actually do care, and want Fedora KDE to be a good experience, and certainly not to get KDE finger-pointed for blocking our general release. So it'd be nice to have some formal way to communicate about our schedules, QA process, and particularly Freeze Exception, Blocker Bugs, and Prioritized Bugs.

We have regular monthly meeting with KDE upstream developers so I'll close this one for now. We can always revisit.