I'm very pleased to announce the release of our new website and documentation using the new toolchain with Hugo and AsciiDoctor. To get more information about the new toolchain please read the FreeBSD Documentation Project Primer[1], Hugo docs[2] and AsciiDoctor docs[3]. Acknowledgment: Benedict Reuschling <bcr@> Glen Barber <gjb@> Hiroki Sato <hrs@> Li-Wen Hsu <lwhsu@> Sean Chittenden <seanc@> The FreeBSD Foundation [1] https://docs.FreeBSD.org/en/books/fdp-primer/ [2] https://gohugo.io/documentation/ [3] https://docs.asciidoctor.org/home/ Approved by: doceng, core
25 lines
1.4 KiB
Text
25 lines
1.4 KiB
Text
---
|
|
title: "Bug Reports"
|
|
sidenav: support
|
|
---
|
|
|
|
include::shared/en/urls.adoc[]
|
|
|
|
= Bug Reports
|
|
|
|
== Problem Report Database
|
|
|
|
* https://bugs.FreeBSD.org/search/[Search Current Problem Reports]
|
|
* https://bugs.FreeBSD.org/submit/[Submit a New Problem Report]
|
|
|
|
A problem report, or _PR_, 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.
|
|
|
|
Problem reports begin in the _open_ 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.
|
|
|
|
== How to Submit a Problem Report
|
|
|
|
Problem reports are submitted to the development team with the https://bugs.FreeBSD.org/submit/[web form]. An account will need to be created before a bug can be submitted. Please note that messages sent to a mailing list are _not_ tracked as official problem reports, and may get lost in the noise!
|
|
|
|
Before submitting a problem report, please read the link:{problem-reports}[Writing FreeBSD Problem Reports] article. This article describes when to submit a problem report and what to include. Some useful background information is also contained in the link:{pr-guidelines}[Problem Report Handling Guidelines] article.
|
|
|
|
FreeBSD problem reports are tracked using http://www.bugzilla.org/[Bugzilla].
|