Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I moved this to a new thread because the subject here didn't really
accurately portray the direction of the conversation but I wanted to say I
have uploaded the latest flowchard:

https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg


I wasn't sure how or if I needed a wiki page or if I should just link to
the jpg in the Useful Links section of the Bug Triage wiki page. Any
thoughts? If you could respond on the other thread (more accurate subject)
that would be great, if not here is fine. Thanks all for the input, I think
that this is at least a decent start.


Joel

On Mon, Jun 18, 2012 at 10:57 AM, Joel Madero <jmadero.dev@gmail.com> wrote:

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@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



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.