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

Source string Read only

(itstool) path: glossdef/para
Context English 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:
Initial state; the problem has been pointed out and it needs reviewing.
The problem has been reviewed and a solution is being sought.
Further work requires additional information from the originator or the community; possibly information regarding the proposed solution.
A patch has been committed, but something (MFC, or maybe confirmation from originator) is still pending.
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.
A problem report is closed when any changes have been integrated, documented, and tested, or when fixing the problem is abandoned.
The <quote>patched</quote> state is directly related to feedback, so you may go directly to <quote>closed</quote> state if the originator cannot test the patch, and it works in your own testing.
Types of Problem Reports
While handling problem reports, either as a developer who has direct access to the Problem Reports database or as a contributor who browses the database and submits followups with patches, comments, suggestions or change requests, you will come across several different types of PRs.
<link linkend="pr-unassigned">PRs not yet assigned to anyone.</link>
<link linkend="pr-assigned">PRs already assigned to someone.</link>
<link linkend="pr-dups">Duplicates of existing PRs.</link>
<link linkend="pr-stale">Stale PRs</link>
<link linkend="pr-misfiled-notpr">Non-Bug PRs</link>
The following sections describe what each different type of PRs is used for, when a PR belongs to one of these types, and what treatment each different type receives.


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: glossdef/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/pr-guidelines.pot, string 31