Bug#735261: mutiple upstream bugs
On Sun, Jan 18, 2015 at 6:18 PM, Shai Berger wrote:
>> Both grave and critical refer to actual data loss. Using the term
>> serious isn't particularly useful since that falls outside those two
>> categories anyway.
>>
>
> Again, you're being tautological, repeating your terms rather than defining
> them.
Without some form of tautology, everyone's favorite itch would get the
highest severity. Nothing would get done that way, so the project
created roughly defined bug severities. Unfortunately language is not
black and white, so often enough people come along with perceptions
that differ from the project at large, and these kinds of discussion
ensue without productively accomplishing anything.
>> The description of the "important" may help correct the ongoing
>> misperception: https://www.debian.org/Bugs/Developer#severities
>>
>
> In my book, "a major effect on the usability of a package" means I can't do
> what I want (easily enough). The case here -- "I told the program something
> and it forgot it" -- is data loss.
The program can't do read/unread flags correctly. That falls under
the first category. Never did it forget the actual content of the
mail, which would be actual data loss.
Unfortunately, this itch isn't severe enough to block the upcoming
release. If it somehow gets fixed in the meantime, you can always
plea your case to the release team to consider accepting it.
Can we please move on?
Best wishes,
Mike
Reply to: