Each PR goes through a defined series of states between origination and closure. The submitter of a PR receives notification automatically via E-mail of any state changes.
The initial state of a Problem Report. This means the PR has been filed and the responsible person(s) notified.
The responsible person has analyzed the problem. The analysis should contain a preliminary evaluation of the problem and an estimate of the amount of time and resources necessary to solve the problem. It should also suggest possible workarounds.
The problem has been solved, and the submitter has been given a patch or other fix. The PR remains in this state until the submitter acknowledges that the solution works.
Work on the problem has been postponed. This happens if a timely solution is not possible or is not cost-effective at the present time. The PR continues to exist, though a solution is not being actively sought. If the problem cannot be solved at all, it should be closed rather than suspended.
Work on the problem has been permanently abandoned. This state is for problems where there is no possible way to continue examining the PR, e.g. someone reported that their machine crashed once, in an old version of NetBSD, and could never reproduce it; someone no longer has the hardware needed to reproduce the problem. The purpose of the "dead" state, as distinct from the "closed" state, is so that people searching the database can quickly ascertain that a problem is not known fixed.
A Problem Report is closed ("the bug stops here") only when any changes have been integrated, documented, and tested, and the submitter has confirmed the solution.