# The form data below was edited by perforce # 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 givenjob 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/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000376 Status: closed Project: tjuricek-file-system-client Severity: A ReportedBy: tjuricek ReportedDate: 2015/10/08 14:34:03 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:24 OwnedBy: tjuricek Description: Implement rename and handle "backup" processes I'm discovering a lot of tools (RubyMine, etc) will write to a temporary backup file, then rename it back to the original file. This will be interesting when it comes to figuring out the correct p4 operations to run in the background. We may end up having lots of things like: rename a -> a_old create a_bak write a_bak rename a_bak -> a unlink a_old ... with *lots* of getattr and getattrx calls in between. If a does exist in the perforce server, what we really want, in the end is "p4 edit a" once that madness is all cleaned up. DevNotes: Type: Feature