# 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/Problem].  Required.
#                 Feature and Bug are common terms.
#                 A Problem is 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-818

Status:	open

Project:	perforce-software-sdp

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2022/08/25 10:34:36

ModifiedBy:	tom_tyler

ModifiedDate:	2022/08/25 10:34:36

OwnedBy:	tom_tyler

Description:
	Simplify SDP version and deprecate SDP_VERSION and SDP_DATE.
	
	Deprecate the SDP_DATE and SDP_VERSION counters.
	
	Some changes needed:
	* The p4_vars.template must be changed to remove REPL_SDPVERSION.
	Change from: export SDP_VERSION="REPL_SDPVERSION"
	Change to:   export SDP_VERSION="$(cat /p4/sdp/Version)"
	* The sdp_upgrade.sh will handle the new p4_vars.template during the
	next SDP upgrade.
	* The upgrade.sh will need to be aware of these counters.
	* The SDP Health Check script will need to NOT break.
	* Beware of impact to 'mkdirs.sh' when run with '-test'
	* Review configure_new_servers.sh so it doesn't set SDP_* counters.
	
	For the original 2007 pre-replication era of SDP, idea of having the
	managed p4d data set be aware of the SDP version made sense; back
	then the guidance was to version the SDP along with the customer's
	data. In modern times, this concept is obsolete.  The SDP can manage
	multiple p4d data sets (aka SDP instances) on a given machine, but
	those data sets are extended via replication and proxies to many
	machines.  The SDP version is bound to the machine, not the data set
	it manages. In fact the SDP can be different on different machines
	with the same data set.

Component:	env

Type:	Feature