Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <46E5E3DF.5090904@roguewave.com>
Date: Mon, 10 Sep 2007 18:39:59 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: severity of issues in Jira
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

To help with prioritization of issues I've added a new custom field
to stdcxx issues in Jira, called Severity, with the following values
in the order of decreasing severity:

1. Runtime Error (e.g., crash including abort, deadlock or livelock,
    and certain cases of data corruption such as buffer overruns and
    other types of undefined behavior that could potentially lead to
    crashes).
2. Binary Incompatibility (e.g., errors at load time due to
    unsatisfied references to symbols that have changed or been
    removed, or undefined behavior as a result of incompatible
    changes).
3. Incorrect Behavior (i.e., any otherwise well-defined behavior
    that's different from the documented behavior).
4. Compiler Error (i.e., a compilation diagnostic including internal
    compiler errors).
5. Linker Error (same as above but for the linker).
6. Inefficiency (including speed or space inefficiencies).
7. Compiler Warning.
8. Linker Warning.

Are there any suggestions for new values or changes to the ones I've
added, or to the assigned priorities?

Martin