# 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: BBI-2 Status: closed Project: perforce_software-p4bbi Severity: B ReportedBy: tom_tyler ReportedDate: 2024/12/06 17:40:45 ModifiedBy: tom_tyler ModifiedDate: 2024/12/06 19:31:32 OwnedBy: tom_tyler Description: Retool to use 'p4 reconcile'. Prior to 'p4 reconcile', the BBI used a series of commands to figure out what changed in a workspace. Commands searched for newly added files, newly added symlinks, deleted files, and modified files. Now 'p4 reconcile' does that more efficiently, and all in one step. As a bonus, this will add automatic detection to P4BBI, as 'p4 reconcile' detects renames. (It uses a heuristic which amounts to a guess, rather than being truly deterministic, but it's proven to be good enough to be helpful -- so far perfect in my experience). This will also fix a problem encountered when files with '@' in the filename are deleted between baseline updates. The older method of using 'p4 diff -sd ... | p4 -x - delete' failed with such files, but 'p4 reconcile' handles that case just fine. Type: Feature