I don't have strong feelings about which mechanism we use, I just want
to be able to indicate that small set of bugs that block usage and testing.
We could use:
- severity field (presumably *blocker*)
- status whiteboard
- dogfood flag
Grant pointed out that the flags are not visible when looking at a list
of bugs. (This is a big limitation of the blocker flag as well. Any
chance a bugzilla upgrade would fix this?)
I have no objection to using the severity field instead. (We are
currently not using the *blocker* severity for any open bugs, btw. A
scan of resolved bugs that used this flag suggests a different usage --
if we do go this route we'd need to be consistent in how we use the
severity status.)
Cheers,
Katie
Philippe Bossut wrote:
I'm not disagreeing and I'm fine raising the severity and priority so
that we get to these bugs fast. If we consider those as "functional
tests that are not automated" cases, then, yes, they should be fixed
immediately.
May be we shouldn't have added the flag then, it's not adding much to
the set of existing fields.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
