# 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 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-389 Status: punted Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2019/04/10 08:32:29 ModifiedBy: tom_tyler ModifiedDate: 2021/01/29 15:53:20 OwnedBy: tom_tyler Description: Made upgrade.sh be standalone and backward compatible. The upgrade.sh script should be standalone and backward-compatible. By standalone, the intent is that it not have any dependency on the current SDP version, so that the upgrade.sh script can work safely with older SDP versions. Generally, SDP should be upgraded as a package due to various dependencies, but this one script needs to be able to be deployed with older SDP versions. This must also be aware of change in p4d over time, and work with any P4D version from 2014.1. This intentionally excludes support for P4D 2013.3, which had its own special upgrade procedure and custom SDP upgrade script, as P4D 2013.3 required a rebuild from a checkpoint. It must avoid using '-J off', as this is bad with 2018.2 (losing journal entries related to the "tech preview" of Extensions) and disallowed by P4D 2019.1. DevNotes: 2021-01-29 ttyler: Punting my own job, due to newer and better strategy of making SDP upgrades easier with SDP r21.1+, so that the ugprade script is not stand-alone. Also, stand-alone would have too great a risk of version skew issues. Component: core-unix Type: Feature