Cleaning bug list

[Joel Madero]

I agree with the save comment, I'll change that right now. Also
realized I didn't put a note in for regressions so I added to the
bottom notes:

**Regressions**
Special attention should be paid to regressions. In most cases a
regression calls for an increase in priority but in some cases it will
not. If the regression is not elevated to a higher priority, a comment
may be useful to explain why this decision was made


Joel

On Mon, Jun 18, 2012 at 10:54 AM, Petr Mladek <pmladek at suse.cz> wrote:
> Joel Madero píše v Po 18. 06. 2012 v 09:32 -0700:
>> Version 2, changed orientation and tried to take comments into
>> account. Let me know what you all think.
>
> It is much better readable. I finally got a better picture :-)
>
> Well, I think that it still need some thinking. You set "inability to
> safe" as major. I think that it should be blocker. The application
> would be almost useless with this bug ;-)
>
>
> I suggest the following changes in the top levels:
>
>   Q: "Does bug cause crash, loss of data[*], inability to install,
>       broken core function, e.g. inability to safe any writer
>       documents, print?
>
>    + A: "yes":
>        => Q: "Does it affect almost all users within everyday usage and
>               is it a regression?"
>                + A: "yes" => blocker, highest, MAB
>                + A: "no"  => critical, high, MAB
>                  I would leave the
>
>
>    + A: "no"
>        => Q: "Does bug involve a serious glitch such as tediously
>               slow, inability to open particular documents, install
>               some extensions, print on some printers?
>
>                + A: "yes": => "major", high
>
> IMHO, the rest might stay as is. Well, it would be great to create
> several examples also for the other categories. I do not have power to
> invent them now, though ;-)
>
> [*] Note that data loss might be caused by incomplete import. If it is
> not a regression, it might be marked by developers as an enhancement.
> Note that it needs many developer/years to support some file formats.
> OOXML format is described on several thousands of pages...
>
> I am very happy with the progress and the state.
>
> Thanks a lot for working on it.
>
>
> Best Regards,
> Petr
>