This is the mail archive of the
frysk@sourceware.org
mailing list for the frysk project.
Re: Bugzilla tickets, severity, and common courtesy
- From: Stan Cox <scox at redhat dot com>
- To: Frysk List <frysk at sourceware dot org>
- Date: Thu, 21 Jun 2007 10:39:55 -0400
- Subject: Re: Bugzilla tickets, severity, and common courtesy
- References: <20070621021643.GJ3085@ca-server1.us.oracle.com>
Severity level definitions leave room for interpretation (sort of like
the C standard, heh heh), but these are the severity definitions that
the Red Hat support team uses.
severity 4 (enhancement in bugzilla) General usage questions,
recommendations for future product enhancements or modifications. There
is no impact on the quality, performance or functionality of the
product.
severity 3 (minor in bugzilla) - Medium-to-low impact problem which
involves partial, non-critical
functionality loss. One which impairs some operations but allows the
customer to continue to function. This may be a minor issue with limited
loss or no loss of functionality or impact to the customer's operation
and issues in which there is an easy circumvention or avoidance by the
end user. This includes documentation errors.
severity 2 (normal in bugzilla) High-impact problem in which the
customer's operation is disrupted but there is capacity to remain
productive and maintain necessary business-level operations.
severity 1 (critical in bugzilla) Catastrophic problems which severely
impact the Customer's ability to conduct business. This may mean that
the customer's systems and/or product are down or not functioning and no
procedural work-around exists. Severity 1 also applies for issues that
result in an emergency condition that cause a serious security breach.