The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

_
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
Context English State
_ translator-credits
Problem Report Handling Guidelines
FreeBSD is a registered trademark of the FreeBSD Foundation.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/pr-guidelines/article.xml 51348 2017-12-30 22:56:56Z eadler $
These guidelines describe recommended handling practices for FreeBSD Problem Reports (PRs). Whilst developed for the FreeBSD PR Database Maintenance Team <email>freebsd-bugbusters@FreeBSD.org</email>, these guidelines should be followed by anyone working with FreeBSD PRs.
<personname><firstname>Dag-Erling</firstname><surname>Smørgrav</surname></personname>
<personname><firstname>Hiten</firstname><surname>Pandya</surname></personname>
Introduction
Bugzilla is an issue management system used by the FreeBSD Project. As accurate tracking of outstanding software defects is important to FreeBSD's quality, the correct use of the software is essential to the forward progress of the Project.
Access to Bugzilla is available to the entire FreeBSD community. In order to maintain consistency within the database and provide a consistent user experience, guidelines have been established covering common aspects of bug management such as presenting followup, handling close requests, and so forth.
Problem Report Life-cycle
The Reporter submits a bug report on the website. The bug is in the <literal>Needs Triage</literal> state.
Jane Random BugBuster confirms that the bug report has sufficient information to be reproducible. If not, she goes back and forth with the reporter to obtain the needed information. At this point the bug is set to the <literal>Open</literal> state.
Joe Random Committer takes interest in the PR and assigns it to himself, or Jane Random BugBuster decides that Joe is best suited to handle it and assigns it to him. The bug should be set to the <literal>In Discussion</literal> state.
Joe has a brief exchange with the originator (making sure it all goes into the audit trail) and determines the cause of the problem.

Showing only subset of the strings as there were too many matches.

Component Translation Difference to current string
The following strings have the same context and source.
Translated FreeBSD Doc (Archived)/articles_committers-guide
Translated FreeBSD Doc (Archived)/articles_bsdl-gpl
Translated FreeBSD Doc (Archived)/articles_contributing
Translated FreeBSD Doc (Archived)/books_arch-handbook
Translated FreeBSD Doc (Archived)/articles_remote-install
Translated FreeBSD Doc (Archived)/articles_explaining-bsd
Translated FreeBSD Doc (Archived)/articles_serial-uart
Translated FreeBSD Doc (Archived)/books_faq
Translated FreeBSD Doc (Archived)/articles_building-products
Translated FreeBSD Doc (Archived)/articles_freebsd-questions
Translated FreeBSD Doc (Archived)/articles_geom-class
Translated FreeBSD Doc (Archived)/articles_ipsec-must
Translated FreeBSD Doc (Archived)/articles_gjournal-desktop
Translated FreeBSD Doc (Archived)/articles_mailing-list-faq
Translated FreeBSD Doc (Archived)/books_developers-handbook
Translated FreeBSD Doc (Archived)/articles_pgpkeys
Translated FreeBSD Doc (Archived)/articles_leap-seconds
Translated FreeBSD Doc (Archived)/books_fdp-primer
Translated FreeBSD Doc (Archived)/articles_linux-users
Translated FreeBSD Doc (Archived)/articles_cups

Loading…

No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatching line breaks: Spanish, Portuguese (Brazil)

Reset

Source information

Context
_
Source string comment
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
Flags
read-only
String age
a year ago
Source string age
a year ago
Translation file
articles/pr-guidelines.pot, string 1