P4DTI issue job000001

TitleThe P4DTI project has no system for planning and tracking change
Assigned userRichard Brooksby
DescriptionThe P4DTI project has no system for planning and tracking change.
AnalysisThe project should use a combination of Perforce jobs and the change management process. This will allow us to develop and refine the change management process, for use with and by Perforce, and for the upcoming presentation at the Perforce User Conference in 2000-09. It will help us to become familiar with Perforce jobs, which is necessary for the p4dti project. It will provide us with test cases for the p4dti project. We can apply the project to itself to get test cases: 1. a project that wants to migrate from using jobs to using a defect tracker; 2. integrating with a defect tracker without messing up your existing job data.
How foundinspection
Created byRichard Brooksby
Created on2000-06-07 13:21:04
Last modified byGareth Rees
Last modified on2001-12-10 18:55:24
History2000-06-07 RB Created.
2000-06-07 RB Analysed.
2000-11-21 RB Closed -- we're using jobs and have been for a while.


Change Effect Date User Description
5631 closed 2000-12-07 15:29:25 Gareth Rees Added Python script known_issues.py to generate a formatted list of open critical and essential defects for the p4dti project; this can then be incorporated into the readme.txt for the release.
Updated the release build procedure to refer to this.