Bugzilla

[Daniel Berlin]

On Sunday, February 23, 2003, at 05:15  PM, Nathanael Nerode wrote:

> I'm wondering what changes are going in along with the Bugzilla
> transitions.  I don't care who's allowed to add
> components/versions/milestones, but I would like:
>
> -- Currently bugs have a 'class' and a 'category'.  I assume that 
> 'category' will become 'component'.
Yes.

>   (Am I wrong?)  What will happen
> to the exceedingly useful 'class'?
It currently gets dropped during conversion.
I'd rather not map it to severity (which is possible), since it isn't 
quite the same.
A severity of "critical" tells you something. A severity of 
"ice-on-legal-code" tells you nothing about the *severity* of the bug.

That said, one can do the same thing class used to do in nicer ways.

You could do it with keywords (which is what the mozilla guys do, 
AFAIK, and probably the best way), or use some combination of severity 
and component to say what class used to say, depending on whether the 
class was really a component (ie documentation bugs. Documentation is a 
component, thus, a class).
Adding a new dropdown field for class is possible, but i honestly think 
it would just confuse users to have a class, component, and severity.

>   Will it be preserved essentially
> as-is?  (I'd approve of that...)

I can throw it into the keywords field automatically if you like, but 
it'll be a few days to get it right.
>
> -- I'd like to get an additional 'class' added: 'warnings'.  These 
> would be 
> bugs specifically about lack of warnings, confusing warnings, mistaken
> warnings, etc.; it's a large subset of the existing 'sw-bug' bugs.  
> It's
> not really doc-bug or sw-bug, and I think it would be a very useful way
> to separate these out from other behavior bugs.
>
With keywords, you can have a bug with both at once.
The current permissions allow anyone with a gcc.gnu.org account to 
create a keyword.

> --Nathanael