# 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-356
Status: closed
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2018/10/15 09:07:44
ModifiedBy: tom_tyler
ModifiedDate: 2020/05/09 11:14:25
OwnedBy: tom_tyler
Description:
Reduce SDP Core to contain only software supported by Perforce Support.
This will come with a simplification in messaging related to support for the SDP, as described in the README.md file, in the 'Supported Open Source Software' section. Essentially, all remaining software components of the SDP, after this trimming, will be fully supported by Perforce Support (for customers with valid Helix Core licenses and when installed by Perforce Consulting).
Software from the SDP project will be relocated as follows:
* The SDP Core will remain in `//guest/perforce_software/sdp`. It will be smaller, and have a greater emphasis on test coverage with automated tests and consistently maintained documentation.
* The HMS software will go back to being a standalone project in `//guest/perforce_software/hms`. There it will be community supported and/or driven by paid consulting engagements.
* Other parts of the SDP will be moved to a new Workshop project HxAdmin Tools, in `//guest/perforce_software/hxadmin_tools`. There it will be community supported. The HxAdmin Tools will be a collection of tools that are decided to be outside the scope of the Core SDP.
The branch specs SDP_Split_2019.2_HMS and SDP_Split_2019.2_HxAdminTools capture the details
of refactoring, indicating which files in the current SDP will get moved. For details,
see:
https://swarm.workshop.perforce.com/view/spec/branch/SDP_Split_2019.2_HMS
https://swarm.workshop.perforce.com/view/spec/branch/SDP_Split_2019.2_HxAdmin_Tools
== Open Source ==
All 3 products, SDP, HMS, and HxAdmin Tools will remain open source
and remain open to contribution by customers.
The HMS and HxAdmin Tools will be community supported, driven by
customer contributions and paid Consulting engagements.
Component: core-unix
Type: Feature
Release: SDP-2019.2