os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reorganize, modernize, optimize, and miniaturize.

Browse source
This commit is contained in:
Warren Block 2014-06-17 02:40:34 +00:00
parent ff632cbdc6
commit 0ff9a2421a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=45068
1 changed files with 23 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

50
en_US.ISO8859-1/htdocs/support/bugreports.xml
View file

@ -15,49 +15,45 @@
<h2>Problem Report Database</h2>
<p>Current FreeBSD problem reports are tracked using <a
href="http://www.bugzilla.org/">Bugzilla</a>.</p>
<p>A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD
itself. In some cases it may be reporting a mistake in the
documentation (which could be a simple typo). In other cases it may
be a 'wishlist' item that the submitter would like to see incorporated
in to FreeBSD. In many cases a PR contains a port which has been
prepared for inclusion in the FreeBSD
<a href="&base;/ports/index.html">Ports and Packages</a> collection.</p>
<p>Problem reports start 'open', and are closed as the issue they report
is resolved. In addition, each PR is assigned a unique tracking ID
to ensure that it is not lost. Many FreeBSD changes include the
tracking ID of the PR that prompted the change.</p>
<ul>
<li><a href="https://bugs.freebsd.org/bugzilla/query.cgi?format=advanced">View or
search problem reports</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/query.cgi?format=advanced">Search
Current Problem Reports</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">Submit a Problem Report</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">Submit a New Problem Report</a></li>
</ul>
<h2>How to Submit A Problem Report</h2>
<p>A problem report, or <em>PR</em>, can be about any component
of FreeBSD, including problems with the operating system programs, a mistake in the
documentation, or a
new feature that the submitter wishes to see incorporated.</p>
<p>Problem reports may be submitted to the development team by using
the web based
<a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">form</a>.
<p>Problem reports begin in the <em>open</em> state, and are closed when the issue
is resolved. A numeric ID is assigned to each PR for tracking.
Many FreeBSD changes refer to the
PR number that prompted the change.</p>
<h2>How to Submit a Problem Report</h2>
<p>Problem reports are submitted to the development team with
the
<a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web form</a>.
Please note that
messages sent to a mailing list are <em>not</em> tracked as
official problem reports, and may get lost in the noise!</p>
<p>Before submitting a problem report, you might find it useful to
<p>Before submitting a problem report, please
read the <a
href="&base;/doc/en_US.ISO8859-1/articles/problem-reports/">Writing
FreeBSD Problem Reports</a> article. This article describes
when you should submit a problem report, what you are expected
to include in one, and what the best way to submit your problem
report is. Some useful background information is also contained
when to submit a problem report and what
to include.
Some useful background information is also contained
in the <a href="&base;/doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem
Report Handling Guidelines</a> article.</p>
<p>FreeBSD problem reports are tracked using <a
href="http://www.bugzilla.org/">Bugzilla</a>.</p>
</body>
</html>