# The form data below was edited by tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a given job is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Doc/Feature/Problem]. Required. # # Bug: is a problem that is fairly well understood, # e.g. one for which there is a reproduction or clear # articulation of the problem. # # Doc: A Documentation fix. # # Feature: An enhancement request, perhaps adding # a new product features, improving maintainability, # essentially any new software improvement other than # a fix to something broken. # # Problem: a suspected bug, or one without a clear # understanding of exactly what is broken. # # Release: Release in which job is intended to be fixed. Job: SDP-889 Status: open Project: perforce-software-sdp Severity: A ReportedBy: robert_cowham ReportedDate: 2023/03/21 08:06:54 ModifiedBy: tom_tyler ModifiedDate: 2023/03/21 10:59:40 OwnedBy: robert_cowham Description: verify_sdp.sh needs to validate db.config root vs offline_db Drift in the values in db.config are dangerous should we switch - need to be detected and reported! Obviously only appropriate for commit/edge not other replica types. DevNotes: Since data drift between P4ROOT and offline_db occurs whenever a 'p4 configure' set command is done until the next journal rotation and replay occurs, we'll make this a special 'extra' check only done when requested with '-extra drift'. The '-extra' option will work like '-skip', referencing a set of checks. Somewhat the opposite of '-skip', '-extra' will checks not done by default but that can be requested. Envisioned usage is to be called by refresh_P4ROOT_from_offline_db.sh just before the DB swap occurs. Component: core-unix Type: Feature