Adding a bug "Severity:" tag to bug system.
- To: firstname.lastname@example.org (Debian Devel)
- Subject: Adding a bug "Severity:" tag to bug system.
- From: andersee@Dillweed (Erik B. Andersen)
- Date: Fri, 6 Dec 1996 14:19:39 -0700 (MST)
- Message-id: <m0vW7gK-000KF9C@Dillweed>
- In-reply-to: <199612062041.OAA12913@Starbase.NeoSoft.COM> from "Vociferous Mole" at Dec 6, 96 02:41:44 pm
Vociferous Mole wrote:
> > I now think the best way to accomplish my goal here is to simply add
> > an optional pseudo-header (Severity:) to the bug reporting system.
> I think this is a good idea.
I vote for this idea as well!
Who is in charge of the bug tracking system, and how would such a change be
implemented such that it would be backward compatible (all old bug reports
do not have this header)? Would somebody need to review all the old bugs
to determine severity? How would an override system be established? This
would be important so that if somebody reports "xboard beats me at chess
too much", and marks it with: "Severity: Critical" their mis-informed
opinion could be adjusted. Additionally, if somebody reports, "xterm
mails my superuser password to USENET twice a day" and marks it as
this would need a little priority adjustment as well. ;-) What guidelines
for bug severity would be used? Maybe something like:
Bug describes a major security hole, such as giving normal users
Bug renders whole system unusable.
Bug would make Debian look stupid and be laughed at.
Bug may render the package useless.
Bug disables important documented package features.
Bug describes documentation which is out of sync with package.
Bug is a request for features which are not currently available,
and should be forwarded to the upstream package developer(s).
Bug makes the package appear or do something ugly, while still
leaving the package completely usable.
Bug involves documentation problems such as spelling, grammar, etc.
I think this addition should be a very high priority, as it will greatly
assist developers, and smooth releases by marking well in advance what
problems exist. A release should then never be made when a bug marked
"Critical" exists. Any thoughts?
Erik B. Andersen Web: http://www.et.byu.edu/~andersee/
2485 South State St. email: email@example.com or firstname.lastname@example.org
Springville, Ut 84663 phone: (801) 489-1231
--This message was written using 73% post-consumer electrons--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com