Lines Matching full:bug
1 page.title=Life of a Bug
30 Reporting bugs is great (thank you!), but what happens to a bug report once
31 you file it? This page describes the Life of a Bug.</p>
48 <p>Here's the life of a bug, in a nutshell:</p>
51 <p>A bug is filed, and has the state "New".</p>
70 <p>New issues include bug reports that are not yet being acted upon. The two
75 The bug report has not yet been triaged (that is, reviewed by an AOSP maintainer.)</p>
79 The bug report has insufficient information to act
80 upon. The person who reported the bug needs to provide additional detail
82 provided, the bug may be closed by default, as one of the No-Action
92 The bug report has been recognized as an adequately
98 Like <em>Unassigned</em>, but the bug has been
102 <p>Typically, a given bug will start in <em>Unassigned</em>, where it
107 <p>In general, if a bug is in one of these Open states, the AOSP team has
109 that bug is likely to get accepted. However, it's impossible to guarantee a
129 behavior described, and was unable to do so. This sometimes means that the bug
131 that the bug was fixed in a later release.</p>
136 that the bug did exist in the reported version but was already fixed in
142 behavior described isn't a bug, but is the intended behavior. This state is
178 This bug has been fixed, and is included in a formal release.
184 This bug has been fixed (or feature implemented) in
193 we tend to do so in periodic "bug sweeps" where we review the database and
