On severities and priorities [was: [Bug 48211] tabbed browsing crashes when key shortcut is used in Konqueror]

Stephan Binner binner at kde.org
Mon Oct 14 21:24:32 BST 2002

On Monday 14 October 2002 16:59, Stephan Kulow wrote:

> I'd suggest you change the severity instead if you think it should be fixed
> asap. The Priority should set by those that the bug is assigned to only

I don't think that mixing of impact severity and priority would be good. Does
"Bug 48334: ksplash earth-icon blinking touches desktop-icon" qualify for 
major, grave or critical? I would rather rate it "minor" but it should have
a high priority because it's visible to all and will cause tons of reports.

Why is the target milestone feature disabled at all? The feature plan suggests 
only "critical" bugs have to be fixed before the release. What about "grave" 
(loss of data[*]) and "major" (a wrong program behaviour that cannot be 
worked around[*]) bugs (e.g. kompare and kview are not usable here because 
they don't find their part)? Why don't they qualify as KDE 3.1 show-stopper?


[*]: definitions according to http://bugs.kde.org/bug_status.html#severity

More information about the kde-core-devel mailing list