Lines Matching full:bug
1 page.title=Life of a Bug
8 Reporting bugs is great (thank you!), but what happens to a bug report once
9 you file it? This page describes the Life of a Bug.</p>
19 <p>Here's the Life of a Bug, in a nutshell:</p>
21 <li>A bug is filed, and has the state "New".</li>
33 <p>New issues include bug reports that are not yet being acted upon. The two
36 <li><b>New</b><p>The bug report has not yet been triaged (that is, reviewed by
38 <li><b>NeedsInfo</b><p>The bug report has insufficient information to act
39 upon. The person who reported the bug needs to provide additional detail
41 provided, the bug may be closed by default, as one of the No-Action
49 <li><b>Unassigned</b><p>The bug report has been recognized as an adequately
55 represented is being tracked in a separate bug database. For example, the bug
56 might have been reported via an internal bug-tracking system,
60 <li><b>Assigned</b><p>Like <code>Unassigned</code>, but the bug has been
63 <p>Typically, a given bug will start in <code>Unassigned</code>, where it
68 <p>In general, if a bug is in one of these Open states, the AOSP team has
83 behavior described, and was unable to do so. This sometimes means that the bug
85 that the bug was fixed in a later release.</p></li>
87 behavior described isn't a bug, but is the intended behavior. This state is
99 <li><b>FutureRelease</b><p>This bug has been fixed (or feature implemented) in
104 <li><b>Released</b><p>This bug has been fixed, and is included in a formal
107 <li><b>Duplicate</b><p>This bug is a duplicate of another, existing bug
116 we tend to do so in periodic "bug sweeps" where we review the database and
119 the list of bug states and the lifecycle described above. When we do this,
