=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/report.html,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- www/report.html 2008/10/09 21:39:26 1.33 +++ www/report.html 2011/04/23 03:10:18 1.34 @@ -63,11 +63,20 @@

How to create a problem report

Always provide as much information as possible. -Try to pin-point the exact problem. Never give vague instructions, -or detail vague problems like "it crashes" or "I get strange interrupt -issues on this one box that I built." Talk to others on IRC or some -other forum to confirm that it is new, repeatable, etc. and make sure -it is not a local problem. +Try to pin-point the exact problem. +Give clear instructions on how to reproduce the problem. +Try to describe the problem with as much accuracy and +non-confusing terminology as possible, +especially if it is not easy to reproduce. +Describing problems like "it crashes" or "I get strange interrupt +issues on this one box that I built", are of no use. +Communicate with others (on the mailing lists, +or any other forum where knowledgeable users congregate) +to confirm that the problem is new and preferably repeatable. +Please try to make sure it is not a local problem +created by broken/unsupported hardware, +or by using unsupported build options or software. +

Please don't start fixing problems that require significant work until you are sure you understand them, especially during our release periods when we must not change major sections of code. @@ -144,8 +153,6 @@ squeeze the facts out of you. On the other hand, if your input files are huge, it is fair to ask first whether somebody is interested in looking into it. -

-Finally, when writing a bug report, please choose non-confusing terminology.

Sending in bug reports

@@ -182,7 +189,7 @@ OpenBSD www@openbsd.org -
$OpenBSD: report.html,v 1.33 2008/10/09 21:39:26 pvalchev Exp $ +
$OpenBSD: report.html,v 1.34 2011/04/23 03:10:18 lum Exp $