Script for fixing software defects

Bug reports are managed through Bugzilla at http://daqbugs.nscl.msu.edu users may directly report non-critical bugs to that system. Bugs are reports of either a software defect, or an enhancement request. Enhancements should be added as part of an existing iteration plan. For the purposes of this document, bug means a software defect.

Defects are resolved either as part of the execution of an iteration plan or, if critical enough, as needed to get an experiment to run. Regardless, the following steps should be followed when fixing a bug.

0. If the defect is not entered in bugzilla, enter it with yourself as the reporter, and the actual reporter as a CC: so that they will be notified of progress on the bug.
1. Using bugzilla, claim a defect marking it as assigned to you. If the defect fix is part of the current iteration plan, mark the item on the plan with your name and indicate the start date.
2. Fix the bug, making changes as needed to existing software.
3. Document the fix in Bugzilla.
4. Confirm the fix works in conjunction with the defect reporter
5. Commit your code changes to the cvs repository.
6. Close the bug in bugzilla. If the defect is being fixed as part of the current iteration plan, indicate the completion date on the plan.