# The form data below was edited by swarm-user # 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: SDP-564 Status: closed Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2020/11/05 10:20:34 ModifiedBy: swarm-user ModifiedDate: 2020/12/29 10:17:40 OwnedBy: tom_tyler Description: Normalized SDP Versioning will start in the SDP r20.1 release. The Version file included in the package, /p4/sdp/Version, will be enshrined as the standard and easy way to determine the SDP version. Starting in the SDP r21.1 release, the upgrade_sdp.sh script (new in the r20.2 release) will upgrade this Version file. The verify_sdp.sh script will be updated to require ths file to exist. A successful verfify_sdp.sh run will be required before uprade_sdp.sh (coming in r21.1) will start upgrade processing. See: SDP-540 - Add upgrade_sdp.sh script to the SDP. DevNotes: This job evolved. Originally there was going to be a new /p4/Version file, but this idea was dropped. The /p4/sdp/Version is clear enough. The spirit of this job, which is to standardize and simplify SDP version checking, is upheld. It was determined that adding yet antoher copy of the Version file would not help with this. This does mean the SDP 'tarball extraction' folder that is symlinked from /p4/sdp is now required on all SDP machines. This is reasonable and it does match how SDP is commonly deployed. There is a failure mode where copying SDP from one machine to another (e.g. via rsync) might miss this, however the verify_sdp.sh will catch that. Component: setup Type: Feature