Lines Matching full:bug
17 # Life of a Bug #
22 Reporting bugs is great (thank you!), but what happens to a bug report once
23 you file it? This page describes the Life of a Bug.
34 Here's the life of a bug, in a nutshell:
36 1. A bug is filed, and has the state "New".
54 New issues include bug reports that are not yet being acted upon. The two
58 The bug report has not yet been triaged (that is, reviewed by an AOSP contributor.)
61 The bug report has insufficient information to act
62 upon. The person who reported the bug needs to provide additional detail
64 provided, the bug may be closed by default, as one of the No-Action
73 The bug report has been recognized as an adequately
81 represented is being tracked in a separate bug database. For example, the bug
82 might have been reported via an internal bug-tracking system,
88 Like *Unassigned*, but the bug has been
91 Typically, a given bug will start in *Unassigned*, where it
97 In general, if a bug is in one of these Open states, the AOSP team has
118 behavior described, and was unable to do so. This sometimes means that the bug
120 that the bug was fixed in a later release.
124 behavior described isn't a bug, but is the intended behavior. This state is
139 This bug has been fixed (or feature implemented) in
146 This bug has been fixed, and is included in a formal
151 This bug is a duplicate of another, existing bug report.
159 we tend to do so in periodic "bug sweeps" where we review the database and
163 the list of bug states and the lifecycle described above. When we do this,
