# The form data below was edited by robert_cowham # 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-512 Status: closed Project: perforce-software-sdp Severity: A ReportedBy: amo ReportedDate: 2020/03/06 02:57:43 ModifiedBy: robert_cowham ModifiedDate: 2020/08/15 01:56:01 OwnedBy: amo Description: upgrade.sh needs clearer documented explanation The documentation needs to be clear that the system admin must not attempt to build any of the symlinks or rename the p4/p4d binaries themselves, as this is handled by the upgrade script. The current documentation explains what is done, but does not make it clear what must not be done. To allow the admin to carry out these tasks themselves, the documentation must remove any ambiguity and prevent the need to ask questions, or avoid the situation where an admin attempts to be helpful and implements some part of the process themselves. Currently, the docs state this: 4.1 Server upgrades Upgrading a server instance in the SDP framework is a simple process involving a few steps. * Download the new p4 and p4d executables for your OS from ftp.perforce.com and place them in /p4/common/bin * Run: /p4/common/bin/upgrade.sh instance * If you are running replicas, upgrade the replicas first, and then the master (outside -> in) -- and -- 5.2.1 upgrade.sh Runs a typical upgrade process, once new p4 and p4d binaries are available in /p4/common/bin. This script will: * Rotate the journal (for clean recovery point) * Apply all necessary journals to offline_db * Stop the server * Create an appropriately versioned link for new p4/p4d/p4broker etc * Link those into /p4/1/bin (per instance) * Run p4d -xu on live and offline_db to perform database upgrades * Restart server Location: /p4/common/bin DevNotes: Component: doc Type: Bug