Ravenbrook / Projects / Perforce Defect Tracking Integration / Version 1.0 Product Sources / Design
Perforce Defect Tracking Integration Project
This document describes the Python classes that implement the Perforce defect tracking integration's replicator daemon and its interface to the defect tracking system.
The purpose of this document is to make it possible for people to maintain the replicator, and to adapt it to work on new platforms and with new defect tracking systems, to meet requirements 20 and 21.
This document will be modified as the product is developed.
The readership of this document is the product developers.
This document is not confidential.
[This document is a placeholder. We've decided not to document the structure of these until they've settled down a bit. RB 2000-10-04.]
[RB 2000-10-05] | "P4DTI Project Design Document Procedure"; Richard Brooksby; Ravenbrook Limited; 2000-10-05. |
[RB 2000-08-30] | "Design document structure" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2000-08-30. |
2000-09-13 | GDR | Created based on [RB 2000-08-18] and [RB 2000-08-30]. |
2000-10-05 | RB | Updated reference to design document procedure [RB 2000-10-05] to point to on-line document. Added placeholder comment. |
2001-03-02 | RB | Transferred copyright to Perforce under their license. |
This document is copyright © 2001 Perforce Software, Inc. All rights reserved.
Redistribution and use of this document in any form, with or without modification, is permitted provided that redistributions of this document retain the above copyright notice, this condition and the following disclaimer.
This document is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this document, even if advised of the possibility of such damage.
$Id: //info.ravenbrook.com/project/p4dti/branch/2001-03-12/integration-kit/design/replicator-class/index.html#1 $
Ravenbrook / Projects / Perforce Defect Tracking Integration / Version 1.0 Product Sources / Design