bug tracking

Andrew Haley aph at redhat.com
Thu Jun 14 01:57:43 PDT 2007


Mark Wielaard writes:
 > On Tue, 2007-06-12 at 08:52 -0700, Mark Reinhold wrote:
 > > > What is a good place to track bugs for distro packages based on openjdk
 > > > like icedtea? We could setup a bugzilla on icedtea.classpath.org to
 > > > track package specific bugs. There is also the bugs.sun.com site but
 > > > that seems really meant for Sun products, not derivatives and community
 > > > based products like icedtea. It has a big drawback that bugs disappear
 > > > in it and only can come out when someone "on the inside" makes them
 > > > public again.
 > > 
 > > A bugzilla on icedtea.classpath.org is probably the best thing for now.
 > 
 > OK, there is http://icedtea.classpath.org/bugzilla now.
 > We will try to keep it just for bugs caused by packaging, the different
 > build setup and replacement classes. And move everything else to the
 > openjdk bug database (or classpath bugzilla if it is caused by a
 > classpath replacement class).

I'm not convinced of the wisdom of that.  Anyone reporting a bug with
IcedTea that is not present in OpenJDK should be able to enter it in
IcedTea's Bugzilla: after all, how are they to know whether a bug is
caused by bad packaging or bad Classpath code?  There's no reason not
to link IcedTea bugs to Classpath bugs if needs be.  Also, from a
practical point of view, I'd like to keep all IcedTea bugs together in
one place.

Andrew.

-- 
Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK
Registered in England and Wales No. 3798903



More information about the distro-pkg-dev mailing list