This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Use of "SUSPENDED" in Bugzilla
On Sun, Feb 19, 2012 at 9:00 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Sun, 19 Feb 2012, Aurelien Jarno wrote:
>
>> > So when should we use SUSPENDED? ?My inclination: SUSPENDED is if there is
>> > known to be something particularly hard about fixing a bug, not simply
>> > that a patch is needed. ?For example, if a bug cannot be fixed by libc
>> > maintainers on their own because various other components need to change
>> > as well, or because ABI implications make a fix hard (e.g. bug 5945). ?And
>> > so many of the SUSPENDED bugs should become NEW (and be unassigned from
>> > anyone they are assigned to).
>>
>> I agree, sounds reasonable.
>
> Thanks, I've added this to
> <http://sourceware.org/glibc/wiki/bugzilla/procedures> (which already had
> some information from 2009 about use in release management, before I added
> things from my recent proposals).
I agree that SUSPENDED should work as described, but with one additional caveat.
The person moving the bug into suspended should attempt to state the
conditions under which the bug will come *out* of the SUSPENDED state.
e.g. SUSPENDED until GCC PR target/XXXX is fixed.
Lastly, SUSPENDED should not be confused with WAITING. The WAITING
state is transient and involves those people directly interacting with
the report.
Cheers,
Carlos.