I really can't say this enough: Please be verbose when submitting bug reports. Please include a copy of your Makefile. Please include all the failing test output. I often do not have the facilities to reproduce your problem, so the only thing to go on is your report. Even if you're submitting a patch I still need all available information to judge if that patch can go in. Having to ask for this information on each bug report eats time unnecessarily.
I've added this to the PATCHING document: Reporting bugs - Often the only information we have for fixing a bug is contained in your report. So... - Please report your bugs via http://rt.cpan.org or by mailing to [EMAIL PROTECTED] RT is preferred. - Please report your bug immediately upon encountering it. Do not wait until you have a patch to fix the bug. Patches are good, but not at the expense of timely bug reports. - Please be as verbose as possible. Include the complete output of your 'make test' or even 'make test TEST_VERBOSE=1' and a copy of the generated Makefile. Err on the side of verbosity. The more data we have to work with, the faster we can diagnose the problem. - If you find an undocumented feature, or if a feature has changed/been added which causes a problem, report it. Do not assume it was done deliberately. Even if it was done deliberately, we still want to hear if it caused problems. -- Thanks, applied. Or, [EMAIL PROTECTED] as we Bulgarian EBCDIC users like to say. -- Jarkko Hietaniemi in <[EMAIL PROTECTED]>
