Priority and Severity definitions:

Issues for all the modules except few modules (Installer, Security, and some Perf related) would be filed in the Issue Tracker available in SailFin Wiki. Priority and severity for the bugs would be assigned by the submitter. Here are the different priorities that could be assigned:

Bug Priority:

P1: Extremely Urgent, fix or patch immediately
P2: Fix or patch required for the next external release
P3: Fix required for customer release
P4: Fix desired for customer release
P5: Fix not required for customer

Bug Severity:

Customer "priority"

Severity is the assessment of how severe a defect is to the people who encounter it. One cannot simply type in a severity rating, instead it is derived from reviewing two variables: the degree of impact on the user; and the functionality affected by the problem. Like the priority, severity is not static and the submitter should be prepared to change it up or down, as they learn more about the reason for the bug and as workarounds are presented.

S1: Need to fix immediately, no possibility of downgrade
S2: Need to fix before customer release, no possibility of downgrade

Use priority 1 or 2 for SHOW STOPPER bugs such as:

  • Any repeatable machine crash, jvm crash, hang or severe performance degradation.
  • High visibility, embarassing bug.
  • Serious, obvious security problem.
  • Data corruption or loss likely to be encountered by a typical user/developer.
  • Inability to test key functionality; any major impact on the user of the functionality; the functionality is very broken.
  • Won't install on reference configurations or other important configurations.
  • Any conformance failures.

Set the priority to 3 if:

  • The bug does not have a serious impact on Quality testing or the customer.
  • There is an acceptable workaround for the bug.
  • Acceptable workarounds do not include:
  • patching a binary
  • rebooting a machine

    Set the priority to 4 if:

  • The bug is a cosmetic bug.
  • The bug has very little impact on the product or the customer.

Set the priority to 5 if:

the bug is a Request for Enhancement (RFE). A RFE can be a bug or a request for improvement to the current functionality.