www/report.html - diff

Return to report.html CVS log

Up to [local] / www

Diff for /www/report.html between version 1.8 and 1.9

version 1.8, 2000/09/17 23:48:35

version 1.9, 2000/09/18 00:08:41

Line 14

<p>

<h2><font color=#e00000>How to report a Problem</font><hr></h2>

<h3><font color=#0000e0>Released versions problem reports.</font></h3>

<h3><font color=#0000e0>Released versions problem reports</font></h3>

Before reporting bugs/problems with released versions,

go through this checklist:

Line 27

changes made between OpenBSD versions.</a>

</ol>

<p>

If nothing looks like it addresses your problem, then it may be time to read

If nothing looks like it addresses your problem, then please become acquainted

with

man sendbug</a>

sendbug(1)</a>

before submitting a bug report.

<p>

Read further down for the <a href="#bugtypes">types of bug reports</a> desired.

<h3><font color=#0000e0>Current version problem reports.</font></h3>

<h3><font color=#0000e0>Current version problem reports</font></h3>

If your problem is with the <i>current</i> source tree rather then a <i>release</i> or

<i>stable</i> tree,

<ol>

<li>Test the problem at least twice, with source updated a few days apart.

<li>Do not report source tree compilation problems, unless they persist.

Line 54

Line 58

</ol>

<br>

<h3><font color=#0000e0>How to create a problem report.</font></h3>

<h3><font color=#0000e0>How to create a problem report</font></h3>

<b>Always provide as much information as possible</b>.

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.

<P>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).

<P>

The following items should be contained in every bug report:

<ol>

<P>

Line 107

Line 123

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

<h3><font color=#0000e0>Sending in bug reports.</font></h3>

<h3><font color=#0000e0>Sending in bug reports</font></h3>

<P>

Try to pin-point the exact problem. Never give vague instructions,

If possible, use the <A HREF="http://www.openbsd.org/cgi-bin/man.cgi?query=sendbug&sektion=1&format=html">sendbug(1)</a> command to get the bug into our tracking system.

or detail vague problems like "it crashes" or "I get strange interrupt

You can follow the tracking system at <A HREF="http://cvs.openbsd.org/cgi-bin/wwwgnats.pl">this web page</a>.

issues on this one box that I built." Talk to others on IRC or some

Sendbug requires that your system can properly send Internet email. If you

other forum to confirm that it is new, repeatable, etc. and make sure

cannot use sendbug on a functional OpenBSD machine, please send your bug report

it is not a local problem. And please don't start fixing problems that

to <A HREF="mailto:bugs@openbsd.org">bugs@openbsd.org</a>.

require significant work until you are sure you understand them, especially

<P>

during our release periods when we must not change major sections of code.

Perhaps what you are sending in is a feature request, not necessarily a bug.

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).

<p>

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