Bugzilla semantics: marking bugs as triaged

Adam Williamson awilliam at redhat.com
Mon Aug 3 16:48:33 UTC 2009

On Tue, 2009-07-21 at 09:33 -0700, Adam Williamson wrote:
> I present three options:
> 1) Leave everything unchanged, both in Bugzilla and in the workflow
> definition. Encourage components which currently use ASSIGNED in a
> non-standard way to use ON_DEV or no state change, as discussed above.
> 2) Change practice for Bugzappers going forward: from some date
> forward,
> all triaged bugs should have the Triaged keyword set rather than being
> changed to ASSIGNED. Do not change anything about any existing bugs.
> 3) Change practice for Bugzappers going forward, as in proposal 2),
> and
> also attempt to convert existing bugs by adding the 'Triaged' keyword
> to
> all bugs in ASSIGNED status on all components which are currently
> actively triaged. 

Sorry for the lateness of this email!

As discussed at the meeting last week, consensus seems to be roughly in
favor of option #2 above. So, let's make that the formal proposal.

Are there any serious objections to proceeding with option #2 - going
forward, bugs will be marked as having been triaged with the use of a
keyword, rather than changing status from NEW to ASSIGNED?

If not, we'll push ahead and make that the new official policy. Thanks!

Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org

More information about the test mailing list