# 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: SDP-911
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2023/05/23 06:11:37
ModifiedBy: tom_tyler
ModifiedDate: 2023/05/23 06:11:37
OwnedBy: tom_tyler
Description:
Fully document and implement parallel checkpoint support.
With the completion of SDP-900, anyone trained on the SDP can find
how to enable parallel checkpoints by looking at the "instance vars"
file, e.g. /p4/common/config/p4_1.vars. That contains the setting
DO_PARALLEL_CHECKPOINTS, with documentation on how to enable parallel
checkpoints.
However, the SDP Guide doesn't yet mention the feature. Changing from
a single-file checkpoint to a directory, while straightforward, is
a far-reaching change with impacts in documention and other scripts.
The command line to recover from a checkpoint directory is slightly
different, and examples in docs and scripts need to be updated.
Somethings that need to be reviewed and probably updated:
* SDP Guide - Add new section on parallel checkpoints.
* SDP Guide - Recovery procedures.
* SDP Guide - Scour for all references to checkpiont ops.
* Scripts that interact with checkpoints:
- load_checkpoint.sh
- mkrep.sh
- edge_dump.sh
- recover_edge.sh
Component: doc
Type: Feature