From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16734 invoked by alias); 21 Jun 2007 14:40:02 -0000 Received: (qmail 16686 invoked by uid 22791); 21 Jun 2007 14:40:01 -0000 X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_50,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Jun 2007 14:39:59 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l5LEduN3027867 for ; Thu, 21 Jun 2007 10:39:56 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l5LEdtZD019160 for ; Thu, 21 Jun 2007 10:39:55 -0400 Received: from multics.rdu.redhat.com (multics.rdu.redhat.com [172.16.57.153]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l5LEdtWv027669 for ; Thu, 21 Jun 2007 10:39:55 -0400 Subject: Re: Bugzilla tickets, severity, and common courtesy From: Stan Cox To: Frysk List In-Reply-To: <20070621021643.GJ3085@ca-server1.us.oracle.com> References: <20070621021643.GJ3085@ca-server1.us.oracle.com> Content-Type: text/plain Date: Thu, 21 Jun 2007 15:00:00 -0000 Message-Id: <1182436795.20944.125.camel@multics.rdu.redhat.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q2/txt/msg00372.txt.bz2 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.