aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/htdocs/support/bugreports.xml
diff options
context:
space:
mode:
authorGabor Kovesdan <gabor@FreeBSD.org>2012-10-01 09:53:01 +0000
committerGabor Kovesdan <gabor@FreeBSD.org>2012-10-01 09:53:01 +0000
commitb4346b9b2dfe86a97907573086dff096850dcb1d (patch)
tree9b951977cbd22dada9b868ac83b1d56791ea3859 /en_US.ISO8859-1/htdocs/support/bugreports.xml
parentbee5d224febbeba11356aa848006a4f5f9e24b30 (diff)
downloaddoc-b4346b9b2dfe86a97907573086dff096850dcb1d.tar.gz
doc-b4346b9b2dfe86a97907573086dff096850dcb1d.zip
- Rename .sgml files to .xml
- Reflect the rename in referencing files Approved by: doceng (implicit)
Notes
Notes: svn path=/head/; revision=39631
Diffstat (limited to 'en_US.ISO8859-1/htdocs/support/bugreports.xml')
-rw-r--r--en_US.ISO8859-1/htdocs/support/bugreports.xml65
1 files changed, 65 insertions, 0 deletions
diff --git a/en_US.ISO8859-1/htdocs/support/bugreports.xml b/en_US.ISO8859-1/htdocs/support/bugreports.xml
new file mode 100644
index 0000000000..67128ba6c1
--- /dev/null
+++ b/en_US.ISO8859-1/htdocs/support/bugreports.xml
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
+"http://www.FreeBSD.org/XML/doc/share/sgml/xhtml10-freebsd.dtd" [
+<!ENTITY title "Bug Reports">
+]>
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <title>&title;</title>
+
+ <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
+ </head>
+
+ <body class="navinclude.support">
+
+ <h2>Problem Report Database</h2>
+
+ <p>Current FreeBSD problem reports are tracked using the <a
+ href="http://www.gnu.org/software/gnats/">GNATS</a>
+ database.</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="&cgibase;/query-pr-summary.cgi">View or
+ search problem reports</a></li>
+
+ <li><a href="&base;/send-pr.html">Submit a Problem Report</a></li>
+
+ </ul>
+
+ <h2>How to Submit A Problem Report</h2>
+
+ <p>Problem reports may be submitted to the development team using the
+ <a href="&cgibase;/man.cgi?query=send-pr&amp;sektion=1">send-pr(1)</a>
+ command on a &os; system or by
+ using the web based <a href="&base;/send-pr.html">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
+ 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
+ in the <a href="&base;/doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem
+ Report Handling Guidelines</a> article.</p>
+
+
+</body>
+</html>