Package: reportbug-ng Version: 0.2007.08.20 Severity: serious --- Please enter the report below this line. ---
Too many users files bugs with a wrong severity because there is no
explanation when choosing severity in reportbug-ng.
Another bug reporting tool does this quite nicely like this:
1 critical makes unrelated 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.
2 grave makes the package in question unusable by most or all users,
or causes data loss, or introduces a security hole allowing access to the
accounts of users who use the package.
3 serious is a severe violation of Debian policy (that is, the problem
is a violation of a 'must' or 'required' directive); may or may not affect
the usability of the package. Note that
non-severe policy violations may be 'normal,' 'minor,'
or 'wishlist' bugs. (Package maintainers may also designate other bugs
as 'serious' and thus release-critical; however,
end users should not do so.)
4 important a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone.
5 does-not-build a bug that stops the package from being built from source.
(This is a 'virtual severity'.)
6 normal a bug that does not undermine the usability of the whole
package; for example, a problem with a particular option or menu item.
7 minor things like spelling mistakes and other minor cosmetic
errors that do not affect the core functionality of the package.
8 wishlist suggestions and requests for new features.
That other tool do also require a detailed justification for choosing a
justification for the report.
For example, if I choose 2 grave, I need to answer one more question:
You are reporting a grave bug; which of the following criteria does it meet?
1 renders package unusable renders the package unusable, or mostly so, on
all or nearly all possible systems on which it could be installed (i.e., not
a hardware-specific bug); or renders
package uninstallable or unremovable without
special effort
2 causes non-serious data loss causes the loss of data on the system that is
unimportant, or restorable without resorting to backup media
3 user security hole introduces a security hole allowing access to
user accounts or data not normally accessible
4 unknown not sure, or none of the above
- and if unknown is chosen, the severity is automatically downgraded to
normal.
Reportbug-ng makes it too easy to file bug reprots with a escalated - or
wrong - severity.
I might have filed this bug reprot with a wrong severity, but I forgot what
the severities meant.
/Sune
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.20-1-vserver-k7
Debian Release: lenny/sid
500 unstable www.debian-multimedia.org
500 unstable ssh.pusling.com
500 unstable ftp.debian.org
500 unstable ftp.de.debian.org
500 testing ssh.pusling.com
500 stable ssh.pusling.com
200 experimental ssh.pusling.com
200 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
=============================-+-===========
python | 2.4.4-6
python-central (>= 0.5.8) | 0.5.14
python-qt3 | 3.17.3-2
python-soappy | 0.11.3-1.8
xdg-utils | 1.0.1-2
--
Do you know how may I ping a 3X mailer?
You neither can ever upload the device to the space bar, nor must forward to a
Fast DLL file on the system.
signature.asc
Description: This is a digitally signed message part.
