public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Stan Cox <scox@redhat.com>
To: Frysk List <frysk@sourceware.org>
Subject: Re: Bugzilla tickets, severity, and common courtesy
Date: Thu, 21 Jun 2007 15:00:00 -0000	[thread overview]
Message-ID: <1182436795.20944.125.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <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.


      reply	other threads:[~2007-06-21 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  2:32 Kris Van Hees
2007-06-21 15:00 ` Stan Cox [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1182436795.20944.125.camel@multics.rdu.redhat.com \
    --to=scox@redhat.com \
    --cc=frysk@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).