# 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-432

Status:	closed

Project:	perforce-software-sdp

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2019/11/14 18:28:29

ModifiedBy:	tom_tyler

ModifiedDate:	2020/09/20 10:12:31

OwnedBy:	tom_tyler

Description:
	Enhance distinction of what is Supported and Unsupported.
	
	This job encompasses these goals:
	
	1. Refactor the SDP structure to help clarify by structure
	what files are, and are not, supported.  The SDP includes
	mix of supported core scripts and unsupported/untested
	samples.  An 'Unsupported' directory is introduced to
	contain unsupported files.
	
	2. Add a 'site' directory to the as-deployed structure of
	the SDP to contain site-specific files, such as custom
	triggers and extensions, which are not supported. Part of
	the value of the SDP is that it provides a standard way to
	deploy custom scripts, both with structure and shell
	environment. This change (and corresponding doc
	changes) will add clarity to what is supported and not
	supported.
	
	3. Enhance the file format for SDP shell environment
	management files generated from templates to make it
	easy to distinguish supported "configuration" from
	unsupported "customization" changes.
	
	The generated files, e.g. p4_N.vars, often need to be
	modified post-installation, which can make them a
	challenge to debug. We will make it easy to discover
	what was "configured" (e.g. scripted substitutions from
	the template) vs. what was "customized" (hand-crafted
	changes made by a customer or consultant, such as addition
	of new shell environment variables for custom trigger scripts).
	
	This includes:
	* p4_vars (generated from p4_vars.template)
	* p4_N.vars (generated from instance_vars.template)
	
	It may also include
	* p4_N.broker.cfg (generated by gen_default_broker_cfg.sh).
	
	This job will drive structural changes and doc changes that
	will make it clear for customers what they can safely change
	without breaking the "warranty seal," and what changes would
	be considered customizations and thus not supported.

Component:	maint

Type:	Feature