Re: Bug workflow page revised

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

 



On Thu, 2009-05-07 at 01:43 -0400, Tom Lane wrote:
> Allen Kistler <an037-ooai8@xxxxxxxxx> writes:
> > What happens when QA on a MODIFIED report fails?  Shouldn't there be a 
> > path to send it back to ASSIGNED for rework?  I do know that RH BZ 
> > currently doesn't allow it.
> 
> According to the status help page
> https://bugzilla.redhat.com/page.cgi?id=fields.html#status

Which, as I mentioned, is for RHEL, where there are real paid people
plugged into this process...

> you push it to FAILS_QA, and then it goes back to ASSIGNED if the
> breakage is bad enough to require a new round of bug investigation.

...this is the bit where the magic happens. "It goes back" seems to
equal "maintainer sets it back".

> If the ON_QA state isn't meaningful for Fedora then this state machine
> probably needs some adjustment for that, but it's not insane on its
> own terms.

The ON_QA / FAILS_QA loop doesn't make too much sense for Fedora as
there is no paid QA group wired into this loop. 'QA' is the reporter. 

I think it should just be a simple setup as the reporter describes;
reporters should be allowed to set bugs back to ASSIGNED from MODIFIED.

At present I'd say you should just post a comment to say the fix doesn't
work for you. It's then the maintainer's responsibility to change back
to ASSIGNED and fix the fix.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux