Source string Read only

(itstool) path: section/para
148/1480
Context English State
<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.
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.
A Problem Report may be in one of the following states:
open
Initial state; the problem has been pointed out and it needs reviewing.
analyzed
The problem has been reviewed and a solution is being sought.
feedback
Further work requires additional information from the originator or the community; possibly information regarding the proposed solution.
patched
A patch has been committed, but something (MFC, or maybe confirmation from originator) is still pending.
suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to take on. If the problem cannot be solved at all, it will be closed, rather than suspended. The documentation project uses <quote>suspended</quote> for <quote>wish-list</quote> items that entail a significant amount of work which no one currently has time for.
closed
A problem report is closed when any changes have been integrated, documented, and tested, or when fixing the problem is abandoned.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: section/para
Flags
read-only
Source string location
article.translate.xml:128
String age
a year ago
Source string age
a year ago
Translation file
articles/pr-guidelines.pot, string 22