Re: Maintainer Responsibilities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

(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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux