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