openstack team mailing list archive
Mailing list archive
Re: What each Bug status should mean
2010/11/24 Jay Pipes <jaypipes@xxxxxxxxx>:
> On Wed, Nov 24, 2010 at 7:46 AM, Soren Hansen <soren@xxxxxxxxxxxxx> wrote:
>> I've set bugs to confirmed once I've decided that it's likely an
>> actual bug. This may include reproducing it or just looking at it and
>> going "oh, yeah, I totally believe that could happen."
> To me, Reproducible == Confirmed.
That's the semantics I attach to it as well. However, sometimes you just
don't really need a (computer driven) python interpreter to reproduce
> I don't really see a need for Triaged at all...that's what the bug
> priority/importance is for.
It just denotes how far along in the triage process the bug is. Setting
it to triaged means (to me) that I've not only verified that the patient
really is injured, but also decided what procedure to perform on them.
Maybe it's just me, but I find that I do one of these things well when
I'm in one mental mode, and need to be in another mental mode to do the
other well, so I find the separation useful.
>> I'd also like to talk about the specific meaning of the importance
>> field to make it less random. Something like:
>> * More than a few people are likely to lose data, or
>> * render some component of OpenStack completely unable to run
>> anywhere, or
>> * leaks sensitive information or lets an attacker alter information.
> And does NOT have a workaround. No bug is critical, IMHO, if there is
> a valid workaround.
>> * Makes some component of Openstack unable to run in most configurations.
>> * Exposes a component of OpenStack to DoS attacks.
>> This would make these importance settings much more useful.
> Some other things to consider in assigning a bug's importance:
> * Number of people affected by the bug. For instance, if the bug only
> affects Mac users or only CentOS users, should not rank as highly as
> others that affect everyone
Agreed. Hence the "more than a few people" and "in most configurations"
phrasings in my examples :)
> * Does it corrupt a datastore? If yes, bump up priority
Agreed. Data loss/corruption bugs should very likely be critical by
default. You know... just as I did in my example :D
Ubuntu Developer http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/