Source string Read only

(itstool) path: section/title

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></email>, these guidelines should be followed by anyone working with FreeBSD PRs.
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.
Joe pulls an all-nighter and whips up a patch that he thinks fixes the problem, and submits it in a follow-up, asking the originator to test it. He then sets the PRs state to <literal>Patch Ready</literal>.
A couple of iterations later, both Joe and the originator are satisfied with the patch, and Joe commits it to <literal>-CURRENT</literal> (or directly to <literal>-STABLE</literal> if the problem does not exist in <literal>-CURRENT</literal>), making sure to reference the Problem Report in his commit log (and credit the originator if they submitted all or part of the patch) and, if appropriate, start an MFC countdown. The bug is set to the <literal>Needs MFC</literal> state.
If the patch does not need MFCing, Joe then closes the PR as <literal>Issue Resolved</literal>.
Many PRs are submitted with very little information about the problem, and some are either very complex to solve, or just scratch the surface of a larger problem; in these cases, it is very important to obtain all the necessary information needed to solve the problem. If the problem contained within cannot be solved, or has occurred again, it is necessary to re-open the PR.
Problem Report State
It is important to update the state of a PR when certain actions are taken. The state should accurately reflect the current state of work on the PR.
A small example on when to change PR state
When a PR has been worked on and the developer(s) responsible feel comfortable about the fix, they will submit a followup to the PR and change its state to <quote>feedback</quote>. At this point, the originator should evaluate the fix in their context and respond indicating whether the defect has indeed been remedied.
This translation Translated FreeBSD Doc/articles_pr-guidelines Introduction
The following strings have the same context and source.
Translated FreeBSD Doc/articles_gjournal-desktop Introduction
Translated FreeBSD Doc/articles_leap-seconds Introduction
Translated FreeBSD Doc/articles_linux-emulation Introduction
Translated FreeBSD Doc/articles_mailing-list-faq Introduction
Translated FreeBSD Doc/articles_pam Introduction
Translated FreeBSD Doc/articles_vm-design Introduction
Translated FreeBSD Doc/articles_freebsd-update-server Introduction
Translated FreeBSD Doc/books_faq Introduction
Translated FreeBSD Doc/articles_geom-class Introduction
Translated FreeBSD Doc/articles_linux-users Introduction
Translated FreeBSD Doc/articles_problem-reports Introduction
Translated FreeBSD Doc/articles_releng Introduction
Translated FreeBSD Doc/books_arch-handbook Introduction
Translated FreeBSD Doc/articles_bsdl-gpl Introduction
Translated FreeBSD Doc/articles_rc-scripting Introduction
Translated FreeBSD Doc/books_developers-handbook Introduction
Translated FreeBSD Doc/articles_building-products Introduction
Translated FreeBSD Doc/articles_committers-guide Introduction
Translated FreeBSD Doc/books_porters-handbook Introduction
Translated FreeBSD Doc/books_fdp-primer Introduction
Translated FreeBSD Doc/books_handbook Introduction
Translated FreeBSD Doc/articles_remote-install Introduction
Translated FreeBSD Doc/articles_fonts Introduction
Translated FreeBSD Doc/articles_freebsd-questions Introduction


No matching activity found.

Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment

(itstool) path: section/title

Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/pr-guidelines.pot, string 9