This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Using GCC Bugzilla for glibc
- From: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- To: Roland McGrath <roland at redhat dot com>
- Cc: Andreas Jaeger <aj at suse dot de>, Petter Reinholdtsen <pere at hungry dot com>, GOTO Masanori <gotom at debian dot org>, <libc-alpha at sources dot redhat dot com>, <bugzilla-masters at dberlin dot org>
- Date: Fri, 19 Dec 2003 02:43:48 -0600 (CST)
- Subject: Re: Using GCC Bugzilla for glibc
> a long time now, and there is no sign of it getting any better. If the GCC
> folks are happy with their bugzilla setup,
Yes, we are. There was some uncertainty when we switched, but we fixed all
initial problems and bugzilla is much better than gnats and we are pretty
happy with it now.
> I honestly don't quite know what the details of "same or separate product"
> being talked about are.
Bugzilla has products and components. Presently, our only product is gcc,
glibc, binutils, and gdb would be other products. Within a product, there
are components; we have the C, C++, F77, ... frontends, middle-end,
optimization, ... components for gcc.
> On the one hand, the GCC folks administering
> bugzilla don't have anything to say about what procedures and policies we
> use for glibc bugs. I don't really see what providing the database service
> has to do with how long our bugs remain unfixed or whatnot, either they
> want to provide the database for another GNU project to use for its own
> purposes or they don't.
I beg to disagree. You are going to use the gcc.gnu.org domain, and we
care about the conduct of projects that want to use this domain. If glibc
or other projects are not making sure that bugs are handled, this will
lead to complaints also to the gcc lists and bugzilla maintainers.
Regarding policies: one of the arguments brought forward for a unified
database was that it is easier to move PRs from one product to another.
That would be much harder, though, if the different projects used
different policies as to what kewords mean, what target milestones mean,
etc. I personally am not sure that we will move bugs from one product to
another very often, I was just expressing the concerns of other members of
the gcc bugzilla group.
Finally: I don't know how help texts are structured, but I imagine that
they are independent of the product. Thus, if you enter a bug report and
click onto the help test for a field, then you get the help text for the
entire database. It would be annoying if we had to have texts that say "If
you enter a PR for gcc, then this fields means X, but if it is for glibc,
then it means Y".
Regards
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/