* Bug reporting To report bugs you need to create a Bugzilla Account. Here are some convenient shortcuts to browse or add bug reports. ** How to make good bug reports
    * Submit a test case, the smaller it is, the better.

    You can do this by clicking on the "Create a new attachment" link. When attaching a file, please set the correct MIME type from the list. For source code, "Plain text" is ok. For tar.gz or .gz files, you can enter "application/x-gzip" in the "Other" text box. * Use http://bugzilla.ximian.com to report the bug.

    In addition to bugzilla, posting to the list is fine if the bug merits larger exposure or design discussions to solve; posting to the list twice or more is just a way to annoy people and make them waste time, specially when you start a new thread about it. * If the test involves libraries or assemblies that are not part of mono, add info about where to download all the dependencies, and how to compile/install them. * If compiling the test case requires more than:

     mcs test.cs 
    provide the full command line you used to compile the test. * If running the test requires more than:
     mono test.exe 
    provide the full command line needed to replicate the bug. * Provide info about the version of the software you're using (both mono and the operating system or relevant libraries). * Provide the output you expect the test case to produce. * Provide the actual output you get from the test case.
A good bug report complies with at least 6 items from the list. If your bug report complies with 3 or less items, it is very poor and it means it will take much more time to fix (when it's not ignored).