bug tracking

[Mark Wielaard]

On Thu, 2007-06-14 at 12:56 +0100, Andrew Haley wrote:
>  > Fair points. But it would be bad not to push any bugs towards the
>  > openjdk/classpath bug databases, because they obviously also would
>  > like to have a full overview of all known issues.
> 
> I have no problem with that, of course.  We can do that in a high-tech
> way or a low-tech way.  The low-tech way is simply to insert a URL
> that points to the Classpath / OpenJDK bug.  That would be OK,
> wouldn't it?

Yes, that would work for a start. Every bug has an URL field now (just
above the Summary), which is currently empty for all bugs.

>  > For now I am seeing http://icedtea.classpath.org/bugzilla a bit as a
>  > "build one to throw one away" project that we can use to see what an
>  > ideal bug tracking solution would be for all the projects involved in
>  > the long term.
> 
> That makes sense.  I hope that we'll be able to use the IcedTea
> bugzilla as a way to ensure that people working on IcedTea don't waste
> time on duplicated effort.  So, if every IcedTea "to do" item has an
> associated Bugzilla entry, the person working to fix it claims the
> bug.

Feel free to create an account and claim any bug!
Anything assigned to bugzilla-at-icedtea.classpath.org
(that is every bug in the database now) is up for grabs! :)

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20070614/766bc72a/attachment.bin