# 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:	HMS-23

Status:	open

Project:	perforce_software-hms

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2021/11/04 08:34:30

ModifiedBy:	tom_tyler

ModifiedDate:	2021/11/04 12:44:40

OwnedBy:	tom_tyler

Description:
	Codify changes to support versioning of P4DTG common/dtg folder.
	
	Currently, we avoid versioning the /p4/common/dtg folder in the SDP
	structure where P4DTG runs, because P4DTG puts a mix of static
	configuration files (which should be versioned) and dynamic files
	including certain XML and log files (which should not be versioned)
	in the same directory.
	
	To version that folder would require a versioned P4IGNORE file
	that appears as /p4/common/dtg/.p4ignore.  Then the default
	SDP_STATUS_DIRS setting in sdp_hosts.cfg could be expanded to
	include the /p4/common/dtg folder.
	
	See also: SDP-700 and P4DTG job job108521 (Perforce-internal).

Component:	test

Type:	Feature