On Miércoles 03 Junio 2009 23:35:07 Adam Williamson escribió: > On Wed, 2009-06-03 at 22:57 +0200, Kevin Kofler wrote: > > Steve Grubb wrote: > > > And then should the bug be closed hoping that one day you pull in a > > > package that solves the user's problem? > > > > If the bug is fixed upstream, the Fedora report can be reopened with a > > request to backport the fix (but that should only be done if it's > > important enough that it cannot wait for the next bugfix update getting > > pushed anyway). > > > > Until then, why do we need to have the bug open in 2 places? > > There's an obvious answer to this question: we track the importance of > issues to Fedora via the Fedora bug tracker, not via upstream bug > trackers. There's no way I can mark a bug in the KDE bug tracker as > blocking the release of Fedora 12. Yes, there's the way to do it - we always have tracker bug for most important issues we have found! And not only for new releases like Fedora 12, but for even for new versions in older releases (like current Qt 4.5.1 tracker [1] which blocks this release nearly about one month). If you think your bug is so important and it's blocker, talk to us, we add it to our tracker and then we are discussing progress on every KDE SIG meeting - you can join, you're welcome! If you join us, you can drive Fedora/KDE development even as users and only users... These important blocking bugs are never closed without working solution. [1] https://bugzilla.redhat.com/show_bug.cgi?id=497658 Jaroslav > (longer email on the whole thread coming.) > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org > http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
