Savannah Bug Cleanup

We will do this in two phases

Phase One

Check that

• category
• status
• responsible person

are correct

Notes

Two new categories have been created

• gfal/lcg_util
• dCache

Bugs in the 'data management' category should be reassigned to these two categories where appropriate.

Bug statuses are described in the EGEE document MSA3.4.2 A bug must not be left in state "none"!

Phase Two

Responsible people then check

• priority
• regression tests - mark the bug as a regression test candidate (mechanism to be defined)
• assignment to patches - for priorities > medium, attach to the patch scheduled to fix the bug

Notes

EGEE is currently changing the way priorities are handled because the last review wanted us to tighten up the process. The plan is to introduce triage where bugs are classified with the following priority.

Immediate

This is a critical issue for which an immediate fix must be released. No other non-immediate issues should be integrated into the fix.

High

The defect must be fixed in the next release. A maintenance release may be triggered, or the fix may be integrated into the next scheduled release.

Medium

The fix should be scheduled in a forthcoming release, by attaching to a patch. No constraints on the timescale.

Low

The defect has been accepted as valid, but no release schedule is imposed.

Note that technically this priority is distinct from the severity, which can be set by the user.

A bug is a regression test candidate if it can be tested on a single isolated node (see BugClassificationForRegressionTests). We still have to decide how to register a bug as a regression test candidate for later test writing.

-- OliverKeeble - 15-Feb-2010