On Mon, 11 Apr 2011, Frédéric Buclin wrote:
> Le 10. 04. 11 02:19, Joseph S. Myers a écrit :
> > Likewise. We don't use VERIFIED and CLOSED in GCC, proper text should
> > reflect the existence of only one closed state with a genuine meaning and
> > not mention the others (ideally they'd be completely hidden).
>
> That's not true. VERIFIED and CLOSED are valid bug statuses used in the
> GCC Bugzilla. There are 517 bugs with one of these statuses.
They are not *meaningful* statuses. The standard Bugzilla descriptions
are written in terms of a QA setup that simply does not exist for GCC and
there is no GCC-specific policy, written or unwritten, for these statuses.
The standard "ASSIGNED" description is another one that does not fit well
with GCC; the meaning is supposed to be that the assignee is working on a
fix ("the proper person" is not a meaningful concept here), and the normal
return to NEW is not "given to another person" but the assignee admitting
they are no longer working on a fix and removing themselves as assignee
without adding someone else.
--
Joseph S. Myers
jos...@codesourcery.com
