[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new tag for `status' field in bug database
From: |
Han-Wen Nienhuys |
Subject: |
Re: new tag for `status' field in bug database |
Date: |
Sun, 24 Dec 2006 16:27:53 +0100 |
User-agent: |
Thunderbird 1.5.0.8 (X11/20061107) |
Werner LEMBERG escreveu:
>>> I suggest to add a new value `postponed' to the `status' field in
>>> the bug database. For example, bug #14 deserves this tag IMHO.
>> I'm not sure this is necessary. In some ways, any bug that's more
>> than two weeks old is "postponed".
>
> I don't think so. Other bug databases like bugzilla have a similar
> field. It's a difference between a bug which is not handled, a bug
> which has been partially fixed, and a really fixed bug.
>
>> Besides, isn't the "priority" field supposed to be used for this?
>
> I say no.
>
>> `Low' means that it might not be fixed before the next (major)
>> release, `high' meaning that it should be fixed before the next
>> release?
>
> Again, I don't think so. Why not tell exactly whether a bug can be
> fixed right now or must be postponed for various reasons?
hmm,
agree here. There's a difference between "can't fix don't have time" and
"can't fix requires rearchitecting".
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com