Severity

• critical - This problem must be fixed before any new development or maintenance on this Category can continue.
• serious - The problem must be fixed before the next build or release of the LDAS package.
• non-critical - The problem is not critical to the build or release of LDAS and can therefore be postponed if other higher Severity.

Priority

• high - This problem must be fixed within one working day.
• medium - This problem must be fixed within one working week.
• low - This problem must be fixed within on LDAS build cycle.

Class

• sw-bug - Problems that exist in the current version of the LDAS software.
• hw-bug - Problem with physical hardware.
• support - Problem requires modifications to system files.
• duplicate - The problem is a duplicate of another problem. When this happens, you must specify the problem which it duplicates.
• enhancement - This is a new feature to be added to the system.

Special Notes:

States for resource_file class

• OPEN: open a new problem report as soon as a new resource file change has been identified as needed (even before it is implemented on the LDAS-DEV or Tandem systems)
• ANALYZED: Once the new resource file change has made it onto the LDAS-DEV system and been shown to work correctly, change the state to "analyzed".
• SUSPENDED: Once the new resource file with its associated change has been committed to CVS (after being shown to work on the LDAS-DEV system, then change the state to "suspended".
• FEEDBACK: Once the next LDAS release has been pushed to the sight and the resource files at the sites updated to reflect the new resourse file/variables at ALL sites, then change the state to "feedback".
• CLOSED: After the new release of LDAS is successfully running on ALL sites with the new resource file in place, then the PR can be closed.