Return-Path: Delivered-To: apmail-lucene-hadoop-commits-archive@locus.apache.org Received: (qmail 69815 invoked from network); 5 Dec 2007 23:43:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Dec 2007 23:43:57 -0000 Received: (qmail 87160 invoked by uid 500); 5 Dec 2007 23:43:45 -0000 Delivered-To: apmail-lucene-hadoop-commits-archive@lucene.apache.org Received: (qmail 87130 invoked by uid 500); 5 Dec 2007 23:43:45 -0000 Mailing-List: contact hadoop-commits-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-commits@lucene.apache.org Received: (qmail 87116 invoked by uid 99); 5 Dec 2007 23:43:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2007 15:43:45 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2007 23:43:53 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 774C8D2E6 for ; Wed, 5 Dec 2007 23:43:32 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: hadoop-commits@lucene.apache.org Date: Wed, 05 Dec 2007 23:43:32 -0000 Message-ID: <20071205234332.7444.20769@eos.apache.org> Subject: [Lucene-hadoop Wiki] Update of "Hbase/IssuePriorityGuidelines" by BryanDuxbury X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lucene-hadoop Wiki" for change notification. The following page has been changed by BryanDuxbury: http://wiki.apache.org/lucene-hadoop/Hbase/IssuePriorityGuidelines New page: == Issue Priority Guidelines == This page describes the criteria you should use for deciding what serverity to apply to your issues filed in the HBase JIRA. This is a work in progress and is open to suggestions. 1. Blocker: Should only be used if the issue WILL cause data loss or cluster instability reliably. 1. Critical: The issue described can cause data loss or cluster instability in some cases. 1. Major: Important but not tragic issues, like updates to the client API that will add a lot of much-needed functionality or significant bugs that need to be fixed but that don't cause data loss. 1. Minor: Useful enhancements and annoying but not damaging bugs. 1. Completely new features or completely cosmetic bugs.