1@c $FreeBSD$
2
3@node States
4@section States of Problem Reports
5
6@cindex life-cycle of a Problem Report
7@cindex states of Problem Reports
8@cindex Problem Report states
9@cindex automatic notification
10
11Each PR goes through a defined series of states between origination and
12closure.  The originator of a PR receives notification automatically of
13any state changes.
14
15Unless your site has customized states (see @pxref{states
16file,,,gnats}), @sc{gnats} uses these states:
17
18@table @dfn
19@cindex @emph{open} state
20@cindex initial state (@dfn{open})
21@cindex state---@dfn{open}
22@item open
23The initial state of a Problem Report.  This means the PR has been filed
24and the responsible person(s) notified.
25
26@cindex @emph{analyzed} state
27@cindex state---@dfn{analyzed}
28@item analyzed
29The responsible person has analyzed the problem.  The analysis should
30contain a preliminary evaluation of the problem and an estimate of the
31amount of time and resources necessary to solve the problem.  It should
32also suggest possible workarounds.
33
34@cindex @emph{feedback} state
35@cindex state---@dfn{feedback}
36@item feedback
37The problem has been solved, and the originator has been given a patch
38or other fix.  The PR remains in this state until the originator
39acknowledges that the solution works.
40
41@cindex @emph{closed} state
42@cindex state---@dfn{closed}
43@cindex final state (@dfn{closed})
44@item closed
45A Problem Report is closed (``the bug stops here'') only when any
46changes have been integrated, documented, and tested, and the submitter
47has confirmed the solution.
48
49@cindex @emph{suspended} state
50@cindex state---@dfn{suspended}
51@item suspended
52Work on the problem has been postponed.  This happens if a timely
53solution is not possible or is not cost-effective at the present time.
54The PR continues to exist, though a solution is not being actively
55sought.  If the problem cannot be solved at all, it should be closed
56rather than suspended.
57@end table
58
59