Re: Bug system severities
> Severity values I propose to have are:
> [ `critical', `grave', `normal' and `wishlist', as defined below ]
Having looked at some of the bugs on the bug list I think it might be
useful to have a `difficult' category:
`difficult': this is a real problem which ought to be fixed; however,
doing so would be a mini-project in itself requiring large amounts of
programming effort or interface redesign, which would not be
appropriate as part of normal package maintenance. The bug is not
expected to be fixed in the immediate future.
Eg, #988 (the pty allocation / utmp problem - though there are now
some ideas floating around about that), and the dpkg ought to log
everything and dselect UI rewrite bugs.
Bugs with `Severity: difficult' would not get nag messages; that would
avoid having to classify things as wishlist items just to stop the
nags when in fact they are bugs.
> `critical': makes other software on the system (or the whole system)
> break, or causes serious data loss, or introduces a security hole on
> systems where you install the package.
> `grave': makes the package in question unuseable or mostly so.
> (`severe', `serious' and `important' all have other meanings.)
> `normal': the default value, for normal bugs.
> `wishlist': for any feature request, and also for any bugs that are
> very difficult to fix due to major design considerations. I think
> it's probably worth lumping these together to keep life simple.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
firstname.lastname@example.org . Trouble?
e-mail to email@example.com .