Re: GCC GNATS classes

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> Did I understood correctly that you suggest to keep these and add
> some further ones? 

Yes, that was the intent.

> In that case we probably should rename
> 
>   > sw-bug::Problem requiring a correction to software.
> 
> to something like "unclassified-sw-bug".

Sounds reasonable, but I don't know how GNATS reacts when the first 80
or so reports lose their class... Otherwise, it would be fine with me.

> And I'd like to see "web pages" as a class of its own. :-)

That's rather an addition to the 'Categories:', which groups reports
by sub-product, instead of by sub-problem. Currently, we have the
categories

c++ c debug fortran gc host java libf2c libgcc libobjc libstdc++
middle-end objc optimization other profiling target

The new classes really only apply to the compiler categories, but I'd
rather have them in classes instead of adding even more categories
(like c++-rejected, c++-ice-on-good, ...)

The canonical classes for web pages would be doc-bug (for things that
are incorrectly documented) and enhancement (for things that are
missing).

>  · Is there a possibility to contact responsible maintainers by e-mail
>    every time a new report has been filed? E.g., I would like to get a
>    notification for every web related report.

Yes, you can assign maintainers to categories. For the C++ category,
I'd rather not do that, but for java, or Web, it may be reasonable.

As a matter of fact, you have two lists per category: a single
individual will get automatically responsible, and a list of
individuals will get notified for PRs in a certain category.

See also

http://gcc.gnu.org/ml/gcc-patches/2000-03/msg00061.html

>  · After everything has been tested a bit (more) we should have a 
>    link from our main page to the GNATS system as well as some additional
>    information.

Yes, and I want approval or rejection for the gccbug script I sent
earlier, so the mainline users can perform testing of the system as
well.

Anyway, who is in charge of sourceware these days?

Regards,
Martin