Bugzilla!

It's not perfect. But it is the issue tracking system we use, and we ask that you do, too.



Enter a bug



but please make sure the bug you're reporting doesn't exist yet, you include all relevant information, etc. See this page for more on how to submit bug reports, or try Google.

Submitting patches

Generate patches using cvs diff -u , or diff -u . Please create your patches relative to the root of the cvs module the patch should be applied to. Please compile changes to multiple files in a single patch file. Make sure the patch adheres to the coding standards, and includes appropriate javadoc.

When you've built the patch, file a new bug report in Bugzilla if one does not exist yet, explain the reason behind the patch, how the patch fixes the issues, and add the patch as an attachment.

If your patch is not getting applied or there is no response, start nagging the developers (politely, please :D) on the developers mailing list.

Documentation patches

Please submit documentation patches against the xml sourcefiles used for generating the documentation, and not against the documentation itself.