![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=285086#c2
Christian Boltz
The color change was intentional. We want critical to be the most visible.
Here's a quote from one of our internal docs: [...] It is inappropriate to use "blocker" to indicate that the defect is a ship stopper. Similarly, the value "blocker" should not be used to denote failures in the product itself. For instance, a defect that causes the product to crash whenever you click a button should be classified as a critical. It is not a blocker, even though it prevents testing of the feature exposed by the button.
Huh? At least for openSUSE, "blocker" is indeed used for bugs that block shipment. Not only by community members (who don't know all guidelines etc.), but also by lots of SUSE/Novell staff. AJ: If this change is really intended, bug handling for openSUSE probably needs some changes (just search for blocker bugs ;-) and maybe a mail on opensuse-factory explaining the changes. BTW:
A word about blockers. Blockers represent a unique type of item in Bugzilla. A blocker prevents developers or testers from performing their jobs. [...]
When talking about the openSUSE distribution, things like unbootable systems would qualify as blockers because it's impossible to test such a system. With the new colors, they might be overlooked... BTW 2: If guidelines about bugzilla usage exist, why do they need to be internal? They would be interesting for community members too and might lead to better bugreports. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.