On vr, 2006-05-12 at 23:32 +1200, Matthew Paul Thomas wrote: > >> To make Malone a bit simpler, in a couple of weeks (the exact date is > >> undecided) the Severity and Priority fields for bugs will be merged. > > > > Why would that be simpler? > > Because it will be one less field to twiddle, with hardly any loss of > usefulness.
Given that severity and priority are not the same, I disagree with the "hardly any"... > > Severity and priority are two very different things. There can be > > major bugs with priority wontfix > > "Priority wontfix" doesn't really make sense anyway -- Won't Fix should > be (and eventually will be) a status, like it is in other bug trackers. Great! Will that be the same for duplicate? > > or minor bugs with high priority... > > ... > > If the Priority field determines in which order developers should fix > bugs like that one, who is the Severity field useful for, and for what > purpose? Currently the situation is the reverse: most people are using > Severity to decide which bugs should be fixed first, and not touching > Priority. And the very fact that individual developers can use the > fields two different ways -- or four different ways, if you count using > each as a subdivision of the other -- makes them less useful for > project management. Severity is the impact of the bug on end users, priority is/should be the order in which bugs are fixed. -- Dennis K. Time is an illusion, lunchtime doubly so.
signature.asc
Description: This is a digitally signed message part
-- launchpad-users mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/launchpad-users
