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


Hi,

On Fri, Jan 17, 2014 at 10:18:18AM -0800, bfoman wrote:
This proposal seems do not take into account Priority and Severity
combinations

How so? Or better: What usecase does the new workflow disrespect that worked
before. FWIW, development didnt base anything on priority or severity so far,
so what are we losing?

and IMHO is not possible with editbugs and canconfirm
privileges for everyone. Better to not have Pri-wars in the Bugzilla.

Again: nothing is changing really wrt permission as before everyone had the
permissions too to mark a MAB.

Anyway this workflow should be updated when there will be new bugs triage
policy change:
https://wiki.documentfoundation.org/File:Prioritizing_Bugs_Flowchart.jpg.

Yes. This is not yet a policy change, its about enabling to do one later. But
FWIW, we had:
- most MABs were not in priority highest
- most priority highest were not MAB
suggesting that the flowcharts was hardly followed at all (thus making priority
mostly useless). IF everyone would have followed that flowchart, all priority
highest would also have been MAB, which certainly was not at all the case.

Ultimately, this:

 https://plus.google.com/+KoheiYoshida/posts/ZEPmsBjay8K

is another reason for using priority, which inherently has multiple levels
(unlike MABs) and is an inbuild feature of bugzilla without reinventing the
wheel.

Best,

Bjoern

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.