From owner-svn-doc-all@FreeBSD.ORG Tue Jun 17 02:40:35 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 201B1E9F; Tue, 17 Jun 2014 02:40:35 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0CC9F28B8; Tue, 17 Jun 2014 02:40:35 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s5H2eYfX080474; Tue, 17 Jun 2014 02:40:34 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s5H2eYun080473; Tue, 17 Jun 2014 02:40:34 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201406170240.s5H2eYun080473@svn.freebsd.org> From: Warren Block Date: Tue, 17 Jun 2014 02:40:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45068 - head/en_US.ISO8859-1/htdocs/support X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 02:40:35 -0000 Author: wblock Date: Tue Jun 17 02:40:34 2014 New Revision: 45068 URL: http://svnweb.freebsd.org/changeset/doc/45068 Log: Reorganize, modernize, optimize, and miniaturize. Modified: head/en_US.ISO8859-1/htdocs/support/bugreports.xml Modified: head/en_US.ISO8859-1/htdocs/support/bugreports.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/support/bugreports.xml Sun Jun 15 23:30:03 2014 (r45067) +++ head/en_US.ISO8859-1/htdocs/support/bugreports.xml Tue Jun 17 02:40:34 2014 (r45068) @@ -15,49 +15,45 @@

Problem Report Database

-

Current FreeBSD problem reports are tracked using Bugzilla.

- -

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 - Ports and Packages collection.

- -

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.

- -

How to Submit A Problem Report

- -

Problem reports may be submitted to the development team by using - the web based - form. +

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 + web form. 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, you might find it useful to +

Before submitting a problem report, please read the Writing FreeBSD Problem Reports 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 Problem Report Handling Guidelines article.

+

FreeBSD problem reports are tracked using Bugzilla.