Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epp-dev] Eclipse bug reporting query

By convention, the severity is typically left up to the originator, while the priority is left up to the committer/project to decide.

Typically, if a committer thinks the severity is not correctly set, they will explain what the "meaning" of the different levels are, suggest another, and see if the originator agrees.
In some cases, if it is "obvious", the committer will simply change the severity level, explaining why they did.

The "meanings" used to be more documented in bugzilla itself, but think a few releases ago they decided to say less about it, see
https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_severity
but most projects us the previously defined basic definitions, where (as I recall)

"blocker" means just that, the bug prevents use or testing of the build (for which there is no work-around)
"critical" implies "loss of data" or frequent crashes
"major" implies "loss of function"
"normal" ... default value, typically the correct setting unless one of the other levels fit.
"minor" means something's wrong, but does effect function significantly.
"trivial" means something's wrong, but doesn't effect function (such as spelling errors in doc, etc.).

But overall, it is up to each project do decide how they triage/handle bugs so some variability from project to project will occur.

HTH

(Are you writing a book? A master's thesis? :)

 



From:        Sandeep Krishnan <krishsandy85@xxxxxxxxx>
To:        Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>,
Date:        11/10/2012 12:14 PM
Subject:        Re: [epp-dev] Eclipse bug reporting query
Sent by:        epp-dev-bounces@xxxxxxxxxxx




Hi Ian,

I had a related query. I would appreciate if you could answer this too.

Does the committer also reassign the severity level for the bug? Users may assign severity level of critical, although the bug actually may be only major one. Is it changed by the committer?

Thanks,
Sandeep

On Wed, Nov 7, 2012 at 3:45 PM, Sandeep Krishnan <krishsandy85@xxxxxxxxx> wrote:
Thanks Ian for your reply. That helps a lot.

Sandeep



On 11/7/2012 2:57 PM, Ian Skerrett wrote:

Sandeep,

I am pretty sure not everyone knows which product/component to select when
opening a bug. However, in most cases the committer who triages the bug will
reassign to the correct category.

Ian


-----Original Message-----
From:
epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx] On
Behalf Of Sandeep Krishnan
Sent: November-07-12 3:46 PM
To:
epp-dev@xxxxxxxxxxx
Subject: [epp-dev] Eclipse bug reporting query

Hello,

I have a couple of questions about the bug reporting procedure for Eclipse.
I looked at several bug reports and am wondering if it is possible that one
may not be sure of what product or component the bug is actually present in.
I had the following questions.

1) Do all the end users know the product/component/subcomponent where the
bug is present? What if someone doesn't know?

2) If an end user reports a bug but with an incorrect product/component
field, then do the developers who fix the bug change this field at some
later stage?

I would appreciate any pointers or links to answer these questions.

Thanks,
Sandeep Krishnan


_______________________________________________
epp-dev mailing list

epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev


_______________________________________________
epp-dev mailing list

epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev


Back to the top