===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/report.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- www/report.html 2000/09/17 23:48:35 1.8
+++ www/report.html 2000/09/18 00:08:41 1.9
@@ -14,7 +14,7 @@
How to report a Problem
-Released versions problem reports.
+Released versions problem reports
Before reporting bugs/problems with released versions,
go through this checklist:
@@ -27,15 +27,19 @@
changes made between OpenBSD versions.
-If nothing looks like it addresses your problem, then it may be time to read
-
-man sendbug
+If nothing looks like it addresses your problem, then please become acquainted
+with
+
+sendbug(1)
before submitting a bug report.
Read further down for the types of bug reports desired.
-
Current version problem reports.
+Current version problem reports
+If your problem is with the current source tree rather then a release or
+stable tree,
+
- Test the problem at least twice, with source updated a few days apart.
- Do not report source tree compilation problems, unless they persist.
@@ -54,9 +58,21 @@
-How to create a problem report.
+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.
+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.
+If you are going to write significant amounts of code, check various
+forums to make sure that someone else is not working on the problem
+(saving duplication of effort).
+
The following items should be contained in every bug report:
@@ -107,20 +123,15 @@
Finally, when writing a bug report, please choose non-confusing terminology.
-Sending in bug reports.
-
-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. And 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.
-If you are going to write significant amounts of code, check various
-forums to make sure that someone else is not working on the problem
-(saving duplication of effort).
-
-
+
Sending in bug reports
+
+If possible, use the sendbug(1) command to get the bug into our tracking system.
+You can follow the tracking system at this web page.
+Sendbug requires that your system can properly send Internet email. If you
+cannot use sendbug on a functional OpenBSD machine, please send your bug report
+to bugs@openbsd.org.
+
+Perhaps what you are sending in is a feature request, not necessarily a bug.
New features are accepted, especially with code that implements
your suggested new feature.
If someone else writes code for your new feature, the chances are that
@@ -150,7 +161,7 @@
www@openbsd.org
-
$OpenBSD: report.html,v 1.8 2000/09/17 23:48:35 chris Exp $
+
$OpenBSD: report.html,v 1.9 2000/09/18 00:08:41 chris Exp $