[2174] in Release_Engineering

home help back first fref pref prev next nref lref last post

Severity levels of bug reports

daemon@ATHENA.MIT.EDU (epeisach@ATHENA.MIT.EDU)
Wed Feb 14 18:03:42 1990

From: epeisach@ATHENA.MIT.EDU
Date: Wed, 14 Feb 90 18:03:07 -0500
To: rel-eng@ATHENA.MIT.EDU

I thought you would like to see these:

From X11R4:

standard naming conventions for xbugs severity levels:

very high		catastrophic server failure
high			catastrophic client failure (crash/data loss)
medium high		critical bug, no workaround
medium			critical bug, workaround supplied
low			non-critical bug
very low		aesthetic opinion
enhancement		requests for change in function




From OSF:


Severity Level:

	Incompatibility -- represents a problem which resulted from inability
				to install the software on the machine.
	Fatal -- represents a problem which resulted in a software crash or
			required reboot of the software.
	Critical -- represents a problem which resulted in software malfunction
			or a feature failure and has no work-around.
	Severe -- represents a problem which resulted in software functionality
			limitation but had alternative work-around.
	Minor -- represents a cosmetic type problem.
	Enhancement -- represents a request for enhancement of the software.


home help back first fref pref prev next nref lref last post