Bug workflow page revised

Adam Williamson awilliam at redhat.com
Fri May 8 18:53:43 UTC 2009

On Thu, 2009-05-07 at 00:58 +0200, Niels Haase wrote:
> 2009/5/6 Adam Williamson <awilliam at redhat.com>:
> > Hi, guys.
> >
> > I just got a bit inspired by a QA meeting discussion, and have made
> > substantial revisions to
> > https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow . It should
> > now be a lot more comprehensive and informative about the whole Fedora
> > cycle (and it's also in the right order!)
> Looks good, but I was wondering about the CURRENTRELEASE, DEFERRED and
> NEXTRELEASE resolutions. You wrote that this are used only for the
> RHEL workflow, but if I look at this list http://tinyurl.com/dbaae5
> (all closed bugs from NetworkManager in F10) it shows up many of the
> above resolutions. Sometimes they are set (wrongly) by the developer
> or, with seams to be more problematic, by updates at fedoraproject.org,
> like here https://bugzilla.redhat.com/show_activity.cgi?id=492246 . It
> looks wrong for me, or did I missed something?

Progress report:

indeed, the updates bot currently closes bugs for which an update is
released in a stable Fedora as 'NEXTRELEASE'. Per the RHEL definitions,
this is clearly wrong: NEXTRELEASE is meant to be used for, say, a bug
that's reported in RHEL 5.3 but fixed in RHEL 5.4 (and which won't ever
be fixed in RHEL 5.3).

Previously it closed them as 'CURRENTRELEASE', which is equally wrong:
per the RHEL definitions, CURRENTRELEASE means "The problem described
has been fixed and only ever appeared in unsupported or unreleased

Now, we can have the Fedora process use resolutions to have different
meanings than they do in RHEL, but I think that way madness lies. I've
spoken to the Bugzilla maintainer and we can't yet display one set of
resolutions / statuses for Fedora bugs and another for RHEL bugs, so
we're stuck displaying the same set of resolutions for all bugs.

We could invent a new resolution - FEDORA_UPDATE or something -
but...gneeesh. We have enough frickin' resolutions already.

So I still think the best solution is my original one, bugs closed by
the release of official Fedora updates should be closed as ERRATA. For
RHEL, ERRATA means "The problem described has been fixed and will be
available as an errata update from our support web site. Please check
the site to see if it is currently available for download."; that's
pretty compatible with "We've released an official Fedora update that
fixes the bug".

Jesse Keating gave me some background on this:

<f13> at one time, we decided that "ERRATA" was improper for Fedora
<f13> fedora doesn't issue errata, we issue updates
<f13> yeah, I just know that early on in Fedora's life, "errata" was

but he also opined that now's a good time to revisit this. I agree that
ERRATA would mean something slightly different for Fedora than it means
for RHEL, but that's an improvement on NEXTRELEASE meaning something
*completely* different, and I think it's the best available option given
the constraints we're working with.
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org

More information about the fedora-test-list mailing list