Hi Daniel,
On 2013-04-08 14:00, Daniel Pocock wrote:
On 07/04/13 03:48, Filipus Klutiero wrote:
Package: bugs.debian.org
Severity: wishlist
X-Debbugs-Cc: debian-proj...@lists.debian.org
The ITS currently assigns each ticket a severity. This is very useful
for users, for example by letting them check the worst problems of a
package without having to read its entire ticket list.
Severity is also useful for developers as a means of prioritizing
tickets - for example, if a developer wants to debug LibreOffice, he'd
better start looking at critical, grave and serious tickets rather than
This all comes back to asking the questions
- what are the goals of the project?
- if releasing is a goal, and quality is a factor, how can the bug
tracking best enable quality releases?
Then you come to questions like: what is the metric for quality?
There are other ways to tag or priorities bugs:
- regressions (things that work in squeeze but not wheezy)
- compatibility (e.g. can you call from softphone A to softphone B, and
is it bad release softphones that don't call each other?)
- competition (can users already get the feature in some other distro
and is that bad for Debian?)
Priority is a function of a change's costs and benefits. Both the
change's costs and benefits are difficult to quantify. The benefits are
indeed difficult to quantify, but we already have a way to quantify
benefits to a fair degree (Severity). What's really missing to compute a
priority is an estimation of costs.
As for the considerations you mention, they can be reflected in a
ticket's severity (if we indeed consider that they affect an issue's
importance).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
