Defect Classification Proposal

[marioa]

From Murthy:

All,

I reviewed bug classification for other open source projects (opensuse, eclipse), and opensuse bug classification
is fairly relevant to OpenSAF. Based on that I created the bug classification for OpenSAF. I am attaching the same here.
Lets review it TLC meeting.

Thanks
Murthy

Blocker

Prevents developers or testers from performing their jobs. Impacts the development process.
(Documentation) Missing documentation for a feature contribution
Examples:

Unable to start the OpenSAF services
Unable to upgrade from one release to another (for release which support inservice-upgratde)

Critical

Crash, loss of data, corruption of data, severe memory leak.
(Documentation) prescribes or doesn't warn against actions that cause data loss or corruption.
Examples:

Crash that is repeatable and evident to multiple users
Memory leaks in the standard execution flows, that lead to memory outages.

Major

Major loss of function, as specified in the product requirements for this release, or existing in the current product.
(Documentation) missing, misleading, inaccurate, or contradictory information to the degree that by following the
documentation successful completion of fundamental tasks is unlikely.

Examples:

Feature complaince as specified in the user documentation missing
Feature not working as per advertised compliance (certain AMF redundancy model not working) in SAF services
Regression test case failure from previous opensaf release for SAF services
Missing critical logging information for system debugging.

Minor

Non-major loss of function.
(Documentation) missing, misleading, inaccurate, or contradictory information in the documentation, but successful task completion is probable.
Examples:

Improper log levels in the OpenSAF services
Code doesn't have appropriate function headers.
Code doesn't have proper indentation.
non reproducible errors in infrastructure services
not following proper naming convention for executables and source files of opensaf.

trivial

Issue that can be viewed as trivial (e.g. cosmetic, UI, easily documented).
(Documentation) contains stylistic or formatting issues, but functionality is not hindered.

Examples
Typos in logs strings, CLI help strings, wrong comments etc