Ravenbrook / Projects / Perforce Defect Tracking Integration
Perforce Defect Tracking Integration Project
This is the project plan for the Perforce Defect Tracking Integration project. It is a version plan as described in [RB 1999-05-20, 5].
This document will be modified as the project progresses.
The readership of this document is anyone interested in the project.
This document is not confidential.
This document specifies version 0.0 by giving the planned level at which we meet the most important requirements [GDR 2000-05-24]. Thereafter, for each version we give a table of changes to the specification since the previous version.
| N | requirement met as far as the nice level (excellent) |
| O | requirement met as far as the optional level (better) |
| E | requirement met as far as the essential level (good) |
| C | requirement met only at the critical level (acceptable) |
| P | requirement only partially met (not yet acceptable) |
| X | requirement not met at all (not acceptable) |
Target date: 2000-07-31
This version has the empty implementation.
Note that this isn't even an implementation of the manual architecture [GDR 2000-05-08, 3.6] because that would still require documented procedures and support.
The requirements analysis is moderately useful, though odd, because it shows the requirements that we can meet with no effort and have to avoid violating as we develop (things like project cost, for example).
| Req | Level | Explanation |
|---|---|---|
| 1 | X | Can't relate sources or changes to anything. |
| 2 | X | Doesn't help anyone. |
| 3 | X | Can't ask any questions. |
| 4 | P | The project is open, so the design is documented. |
| 5 | X | Doesn't answer any questions. |
| 21 | X | Extension means whole implementation. |
| 22 | C | Integration design is documented. |
| 23 | N | Integration is open. |
| 24 | N | Uses readily available tools (none). |
| 25 | N | Design is modifiable. |
| 26 | N | Portable in less than 1 week. |
| 27 | X | Not stable yet. |
| 30 | X | Not maintained. |
| 33 | X | Not supported. |
| 63 | X | Not installable. |
| 67 | X | No logging of changes. |
| 69 | X | No defect tracker interface to Perforce. |
| 70 | X | No Perforce interface to defect tracker (repl. is one-way). |
| 76 | N | No effort yet required from Chris. |
| 79 | N | Project cost less than $50K. |
| 84 | X | Will not increase customer good will. |
| 99 | N | Supports all P4S platforms. |
| 100 | N | Supports all DT platforms. |
| 101 | N | Supports all DTC platforms. |
| 102 | N | Supports all databases. |
Target date: 2000-08-14
Supports the TeamTrack defect tracker on Windows NT.
One-way replication from the defect tracker to Perforce, of issues only (not users, groups, fixes, etc).
The replication daemon polls the defect tracker (it is not triggered on changes).
Very limited documentation.
No support for the tracker-client architecture.
| Req | Level | Explanation |
|---|---|---|
| 1 | P | Can "fix" issues within Perforce. |
| 2 | P | Developers can at least see the issues via Perforce. |
| 3 | P | Can ask Perforce about "fixes". |
| 5 | P | Issues and changes can be related but only in Perforce. |
| 6 | E | Integrated with TeamTrack 4.5. |
| 8 | E | Uses TeamShare API. |
| 26 | O | Portable in less than 2 weeks (interface to Perforce). |
| 67 | N | Changes are logged. |
| 84 | P | Marginal effect on goodwill through open web site. |
| 99 | C | Supports P4S on Windows NT |
| 100 | C | Supports DT on Windows NT |
| 101 | C | Supports DTC on Windows NT |
| 102 | P | Supports MS Access. |
Target date: 2000-09-11
Two-way replication of issues only.
| Req | Level | Explanation |
|---|---|---|
| 2 | P | Developers can modify issues via Perforce. |
| 76 | ? | Chris must implement the updates table. |
| 79 | N | Project cost less than $85K. |
Target date: 2000-10-02
Has draft documentation.
Has installation and de-installation procedures.
Suitable for external alpha release.
| Req | Level | Explanation |
|---|---|---|
| 2 | C | It's documented! |
| 63 | C | Installable in less than 40 hours. |
| 84 | P | Alpha release makes customers feel that progress is being made. |
Beta release supporting TeamTrack.
| Req | Level | Explanation |
|---|---|---|
| 3 | C | Can ask Perforce or TeamTrack about "fixes". |
| 63 | O | Installable in less than 8 hours. |
| 69 | E | Someone with basic knowledge of Perforce concepts can read and understand the fixes table. |
| 70 | E | Competent users can edit jobs and so update and transition issues. |
| 76 | O | Chris has implemented the logger, the status field in the fixes table, and the -s option to "p4 submit" and "p4 change". |
| 99 | N | Supports Perforce on any server platform. |
| 100 | O | Supports TeamTrack on Windows NT and Windows 2000. |
| 101 | O | Supports TeamTrack databases on Windows NT and Windows 2000. |
| 102 | O | Supports any TeamTrack database. |
| 106 | E | P4DTI enforces defect tracker's constraints on Perforce. |
| 107 | C | Supports Perforce 2000.2. |
Beta release also supporting Bugzilla.
| Req | Level | Explanation |
|---|---|---|
| 18 | O | Integrated with Bugzilla 2.10. |
| 99 | N | Supports Perforce on any server platform. |
| 100 | O | Supports TeamTrack on Windows NT and Windows 2000; Bugzilla on Linux and Solaris. |
| 101 | O | Supports TeamTrack databases on Windows NT and Windows 2000; MySQL on Linux and Solaris. |
| 102 | O | Supports any TeamTrack database; supports MySQL for Bugzilla. |
Target date: 2001-02-28
Fully documented.
Supported.
Maintained.
Suitable for external public release.
| Req | Level | Explanation |
|---|---|---|
| 2 | C | It's fully documented. |
| 3 | C | Can ask Perforce, TeamTrack or Bugzilla about "fixes". |
| 4 | P | The Integrator's Guide is partly written. |
| 27 | P | Administrator and user experience is similar to 0.5. |
| 30 | C | Maintenance agreement between Ravenbrook and Perforce. |
| 33 | C | Supported by TeamShare and Perforce. Support agreement between Ravenbrook and Perforce. |
| 34 | E | Perforce support are able to answer questions about integrating Perforce with defect tracking systems. |
| 63 | O | Installable in less than 4 hours. |
| 64 | N | Uninstallable in less than 3 hours. |
| 79 | E | Project cost less than $300K. |
| 84 | C | Public release gives people a good feeling. |
| 105 | N | Users can see all Perforce details via link from defect tracker to P4Web. |
| 107 | C | Supports Perforce 2000.2 and 2001.1. |
Target date: 2001-04-01
Includes Integration Kit.
| Req | Level | Explanation |
|---|---|---|
| 4 | C | The Integration Kit is complete and documented. |
| 18 | O | Integrated with Bugzilla 2.10 and 2.12. |
| 20 | E | Integration with defect trackers is possible by people outside Perforce using the Integration kit. |
| 21 | C | Effort required to integrate with a new defect tracker is about 10 weeks. |
| 22 | N | Integration design documentation included in integration kit. |
| 26 | O | Portable to new OS in less than 4 weeks (interface to Perforce, system logging). |
This section lists planned maintenance work on the P4DTI version 1.1, based on GDR's draft maintenance plan [GDR 2001-04-20].
During the maintenance of the P4DTI, Ravenbrook will be:
Responding to support requests, identifying defects and fixing defects in order of importance, following the procedures agreed with Perforce [RB 2001-03-07a], [RB 2001-03-07b].
Developing more test cases, including regression, capacity, performance and response tests, to improve the robustness of the P4DTI.
Target date: 2001-05-14
Works with large TeamTrack databases (thousands of issues).
Works around or fixes job000277, job000278 and job000279.
This became release 1.1.6.
| Req | Level | Explanation |
|---|---|---|
| 115 | N | Capacity not limited by replicator. |
Target date: early 2001-06 (this is when TeamShare plan to release TeamTrack 5 [RB 2001-04-26]).
Supports TeamTrack 5.
Fixes job000310.
This became release 1.1.6.
| Req | Level | Explanation |
|---|---|---|
| 6 | E | Integrated with TeamTrack 4.5 and TeamTrack 5.0. |
Target date: 2001-10-19.
Supports Bugzilla 2.14.
| Req | Level | Explanation |
|---|---|---|
| 18 | O | Integrated with Bugzilla 2.10, 2.12 and 2.14. |
Target date: 2001-12-21
Supports migration from Perforce to the defect tracker.
| Req | Level | Explanation |
|---|---|---|
| 120 | O | Migration from Perforce jobs. |
| 121 | O | Creation of new issues in Perforce. |
Target date: 2002-02-14
Supports Perforce 2002.1. Supports TeamTrack 5.5. Supports Bugzilla 2.14.1. Fixes defects as requested by Perforce support [Thompson 2002-01-07].
| Req | Level | Explanation |
|---|---|---|
| 1 | C | Fix of job000016 means that conflicts are reduced, so databases are more often consistent. |
| 2 | C | Fix of job000016 means fewer manual interventions. |
| 6 | E | Integrated with TeamTrack 4.5, 5.0, and 5.5. |
| 18 | O | Integrated with Bugzilla 2.10, 2.12, 2.14 and 2.14.1. |
| 96 | E | Supports replication from one defect tracker to multiple Perforce servers. |
| 107 | C | Supports Perforce 2000.2, 2001.1 and 2002.1. |
Target date: 2002-07-01
Supports Bugzilla 2.16.1 on Unix/Linux and Bugzilla 2.14.4 on Windows. Fixes defects as requested by Perforce support.
| Req | Level | Explanation |
|---|---|---|
| 18 | O | Integrated with Bugzilla 2.14.4 and 2.16.1 on Linux and Solaris, and with Bugzilla 2.14.4 on Windows. Bugzilla 2.10, 2.12, 2.14, and 2.14.1 are still supported but deprecated. |
Target date: 2003-05-01
Supports most recent Bugzilla releases (2.16.3 and 2.14.5 at the time of writing). Drops support for TeamTrack and for deprecated releases of Bugzilla. Improved and simplified installation documentation.
| Req | Level | Explanation |
|---|---|---|
| 6 | - | This requirement is now obsolete; TeamTrack is no longer supported. |
| 7 | - | This requirement is now obsolete; TeamTrack is no longer supported. |
| 8 | - | This requirement is now obsolete; TeamTrack is no longer supported. |
| 18 | O | Integrated with Bugzilla 2.14.5 and 2.16.3 on Linux and Solaris, and with Bugzilla 2.14.5 on Windows. No longer supports Bugzilla 2.10, 2.12, 2.14, and 2.14.1. |
| 63 | N | Installable in less than 3 hours. |
Target date: 2003-10-01
Allows configurable jobspec. Improved security. Works with Perforce 2003.2. Supports most recent Bugzilla releases (2.16.4 and 2.14.5 at the time of writing).
| Req | Level | Explanation |
|---|---|---|
| 122 | O | Add some new configuration parameters to allow finer control over the fields replicated, and to turn off updating the jobspec. Add code to perform detailed checks on a jobspec and optionally extend it, including scripts to perform these tasks independently. Change the replicator so that when touching an existing job it does not touch any non-replicated fields. |
| 18 | O | Add support for Bugzilla 2.16.4. |
| 107 | C | Add support for Perforce 2003.2. |
Target date: 2004-07-12
Major changes in Bugzilla interface to support Bugzilla 2.18. Also supports Bugzilla 2.16.5, and Perforce 2004.2.
| Req | Level | Explanation |
|---|---|---|
| 18 | O | Add support for Bugzilla 2.18 and 2.16.5. |
| 107 | C | Add support for Perforce 2004.2. |
| [GDR 2000-05-24] | "Perforce Defect Tracking Integration Project Requirements"; Gareth Rees; Ravenbrook Limited; 2000-05-24. |
| [GDR 2001-04-20] | "P4DTI short term plan" (e-mail message); Gareth Rees; Ravenbrook Limited; 2001-04-20. |
| [GDR 2001-12-14] | "Defect resolution priorities" (e-mail message); Gareth Rees; Ravenbrook Limited; 2001-12-14. |
| [RB 1999-05-20] | "Product Quality through Change Management"; Richard Brooksby; Geodesic Systems; 1999-05-20; <URL: http://richard.brooksby.org/1999/05/20/pqtcm/>. |
| [RB 2000-02-02] | "Steps to Defect Tracking"; Richard Brooksby; Ravenbrook Limited; 2000-02-02. |
| [RB 2000-07-12] | "Draft version plan (0.0 to 0.3, up to 2000-10)" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2000-07-12 |
| [RB 2001-03-07a] | "P4DTI Project Procedure for Perforce-reported Defects"; Richard Brooksby; Ravenbrook Limited; 2001-03-07. |
| [RB 2001-03-07b] | "P4DTI Project Procedure for Assisting Perforce Support"; Richard Brooksby; Ravenbrook Limited; 2001-03-07. |
| [RB 2001-04-26] | "P4DTI for TeamTrack 5.0" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2001-04-26. |
| [Thompson 2002-01-07] | "P4DTI Defect prioritization" (e-mail message); Gerry Thompson; Perforce; 2002-01-07. |
| 2000-08-10 | RB | Created based on plan in project overview. |
| 2000-08-30 | RB | Imported full version plan with specifications from e-mail notes. |
| 2001-02-23 | GDR | Added plan for version 1.0. |
| 2001-04-20 | GDR | Added plan for version 1.1. |
| 2001-05-01 | GDR | Added plan for maintenance of version 1.1. |
| 2001-10-16 | GDR | Added retrospective specifications for version 0.4 and 0.5. Wrote specifications for version 1.2 and the migration version. |
| 2002-01-07 | GDR | Added version 1.4. |
| 2002-02-01 | GDR | Added support for TeamTrack 5.5 to version 1.4 plan. |
| 2002-03-14 | NB | Removed support for TeamTrack 5.02 from version 1.4, as per Perforce request. |
| 2002-06-07 | NB | Added version 1.5. |
| 2003-05-08 | NB | Added version 2.0. |
| 2004-07-05 | NB | Add version 2.2. |
Copyright © 2000 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/plan/index.html#25 $
Ravenbrook / Projects / Perforce Defect Tracking Integration