Re: new tag for `status' field in bug database

[Werner LEMBERG]

> > 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?


    Werner