Rockbox mail archive
Subject: Flyspray severity setting
Flyspray severity setting
I think we need some kind of guidelines for these.
First of all, is there any reason for feature requests and patches to have
severity other than normal?
Then, for bugs I suggest the following key:
(please add more bullets here)
o A (previously working) target cannot be used for audio playback
o Possible damage to hardware
o A core feature (e.g., some codec) doesn't work
o A nonpredictable action freezes/segfaults but can be avoided
(e.g., by using some setting)
o Possible damage to data (e.g., filesystem)
o A predictable action freezes/segfaults
o Non-core related annoyances
o Button assignments
* Very Low
o Visual glitches
My 2 cents,
When we're done with these we could deal with priority values and other
IMHO, severity is the least intuitive property.
Received on 2006-09-18
Page was last modified "Jan 10 2012" The Rockbox Crew