Hi Dmitry,
thanks for extending info on what is different in Fuel for Confirmed & Fix
Released statuses [1]

It is pretty hard to go in history of the page now, but I think I like
original OpenStack Imporance description in [2], than Fuel-specific [3]:

> - Critical = can't deploy anything and there's no trivial workaround; data
> loss; or security vulnerability

- High = specific hardware, configurations, or components are unusable and
> there's no workaround; or everything is broken but there's a workaround
So, "can't deploy anything" is Critical. If you can deploy cloud, but it
doesn't work afterwards - is not Critical anymore with current description.
I do not think that it is just High that you can't open Horizon page after

Why don't we stick to the original OpenStack criteria?

> - Critical if the bug prevents a key feature from working properly
> (regression) for all users (or without a simple workaround) or result in
> data loss
> - High if the bug prevents a key feature from working properly for some
> users (or with a workaround)



On Thu, Feb 5, 2015 at 8:22 PM, Dmitry Mescheryakov <
dmescherya...@mirantis.com> wrote:

> Guys,
> I was looking for a page where bug statuses in out LP projects are
> described and found none. Mike suggested to add this to How To Contribute
> page and so I did. Please take a look at the section [1], just to make sure
> that we are on the same page. The status descriptions are located in the
> second from the top list.
> Thanks,
> Dmitry
> [1]
> https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs

Mike Scherbakov
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to