Re: Maintainer Responsibilities

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

 



On Thu, 2009-06-04 at 23:19 +0200, Edwin ten Brink wrote:

> Aside from all discussions in this thread, the current Bugzilla 
> documentation seems quite clear on this topic. Whatever the outcome of 
> the discussion is, I think the documentation which is visible to the 
> end-user (customer), should at least match the common practice/procedure.
> 
> Note also that the discussion is primarily focussed on the Resolution of 
> the bug report, while there are also two Keywords available with respect 
> to upstream. I've quoted the full texts below for reference.

>  From https://bugzilla.redhat.com/describekeywords.cgi

This page doesn't really cover Fedora policy or practice, it covers RHEL
policy and practice, which is not the same thing.

The next revision of Bugzilla will in fact include a link on this page,
directing you to:

https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow

for the Fedora policy and practice. That page says in passing:

"The resolution UPSTREAM can be used by maintainers to denote a bug that
they expect to be fixed by upstream development and naturally rolled
back into Fedora as part of the update process. Ideally, a comment
should be added with a link to the upstream bug report."

but that's just what I wrote when updating the page, it's not based on
any official discussion / agreement, so I made it intentionally vague
and (hopefully) non-controversial.
-- 
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