Ravenbrook / Projects / Perforce Defect Tracking Integration / Project Procedures

Perforce Defect Tracking Integration Project


P4DTI Project Procedure for Perforce-reported Defects

Richard Brooksby, Ravenbrook Limited, 2001-03-07

1. Introduction

This is the procedure for handling defects in the P4DTI product reported by Perforce Software, as requested by Perforce Software [RB 2001-02-20].

The readership of this document is Ravenbrook staff.

This document is not confidential.

2. Procedure

Perforce will assign defects reported to Ravenbrook a severity. Perforce have three levels of severity:

A complete failure of the product, data corruption, serious instability
B important, but not urgent
C nice to have

Ravenbrook will not change the severity without agreement from Perforce.

Here's how the severities correspond to Ravenbrook's priorities:

A critical
B essential
C optional or nice

Here is how Ravenbrook will handle defects of the various severities:

A Defects will be given priority over all other work on the project. A patch or work-around will be issued as soon as possible. When fixed, a new release of the software will be made immediately.
B Defects will be given priority over severity C defects. They will be fixed and rolled into the next release. They won't usually cause a new release to be made.
C Defects will be fixed if there are sufficient resources (time and budget allowance).

A. References

[RB 2001-02-20] "Meeting with Kathy Baldanza, 2001-02-19" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2001-02-20; <http://info.ravenbrook.com/mail/2001/02/20/22-14-58/0.txt>
[RB 2001-03-06] "P4DTI things to do for delivery" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2001-03-07; <http://info.ravenbrook.com/mail/2001/03/06/15-10-17/0.txt>

B. Document History

2001-03-07 RB Created from [RB 2001-03-06].

Copyright © 2001 Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.

$Id: //info.ravenbrook.com/project/p4dti/procedure/perforce-defect/index.html#3 $

Ravenbrook / Projects / Perforce Defect Tracking Integration / Project Procedures