# The form data below was edited by super-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. # # Component: Larger projects may use this optional field to # indicate which component of the project a given # job is associated with. # # Type: Type of job [Bug/Feature]. Required. Job: CBD-24 Status: suspended Project: perforce-software-cbd Severity: C ReportedBy: tom_tyler ReportedDate: 2017/05/17 12:18:53 ModifiedBy: super-tom_tyler ModifiedDate: 2017/05/17 12:22:09 Description: Enable bi-directional stream-spec/*.cbdsst workflow. Provide a workflow that allows developers to modfiy CBD configurations via traditional stream spec edits, or via changes to the *.cbdsst file. A change in either updates the other implicitly via trigger actions. This change will help make CBD automation somewhat more transparent. Implementation Detail: Presently, the CBD trims version specifiers from the versioned form of the stream spec (the *.cbdsst file). This is done for a few reasons: * Earlier versions of P4D didn't support version specifiers in stream specs, so they had to be trimmed off or the server would reject them. P4D 2015.1 supports changelists only as revision specifiers. * CBD supports any valid revision specifier, while P4D 2015.1 supports only changelists. P4D 2015.2 may add support for automatic labels and timestamps. That leaves only static labels (important) and workspaces (not so import) as revision specifiers supported by these CBD scripts outside of P4D. Decision: * CBD automation will detect P4D version: o If P4D < 2014.1, strip all revision specifiers going from *.cbdsst -> live stream spec. o If P4D < 2014.2, strip all revision specifiers going from *.cbdsst -> live stream spec except changelist numbers. o If P4D < 2015.2, strip all revision specifiers going from *.cbdsst -> live stream spec except changelist numbers and automatic labels. Warning: The ability to update stream specs directly had proven a helpful workaround to earlier CBD issues which have since been eliminated. This change would eliminate that flexibility, though it seems it is longer be needed. DevNotes: CBD-SOW-2 Type: Feature