On Tue, 2009-03-10 at 19:10 +0000, Daniel P. Berrange wrote: > On Tue, Mar 10, 2009 at 11:57:10AM -0700, Adam Williamson wrote: > > On Tue, 2009-03-10 at 14:24 -0400, Todd Zullinger wrote: > > > Chuck Anderson wrote: > > > >> https://bugzilla.redhat.com/page.cgi?id=fields.html > > > > > > > > How did you find that? I was looking for it, but couldn't find it > > > > linked from anywhere. > > > > > > It's linked, at least, in the word "Status" at the bottom of each bug, > > > next to the drop-down where you would set the status. > > [snip] > > > Possibly the clearest thing to do would just be to use the same flow > > RHEL uses, even if the names would be a bit odd for Fedora (since we > > don't really have 'Errata' for Fedora releases). Otherwise, the Fedora > > flow should at least be clearly defined somewhere, and explained on that > > page in Bugzilla. > > The Fedora bug flow is defined here: > > https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow > > Although it is lacking clear guidelines on the choice of sub-state for > the CLOSED state. That just requires a little docs work on the wiki. Hehe. I was actually going to link to that page and then didn't, for two reasons: 1) as you say, it fudges the CLOSED resolutions anyway 2) it's being revised (we're working on it today) since NEEDINFO isn't a status these days. -- 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
