# 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-602
Status: suspended
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2021/02/17 11:50:00
ModifiedBy: tom_tyler
ModifiedDate: 2021/02/17 11:50:00
OwnedBy: tom_tyler
Description:
Drop PDFs from SDP package.
Should we drop the generated PDFs from the SDP?
Some thoughts:
* The PDFs bloat the tarball; they're the largest files in the SDP,
even bigger than the executable binaries for Windows like gzip.exe.
* The HTML has much of the niceness of the PDFs, and are almost
universally readable.
* We would leave the ability to generate PDFs in the Makefile, but
change it so they're excluded from packaging process. PDFS could
still be made available for those who want them (though getting them
would require installing AsciiDoc, or ask us for them).
* The PDFs do look nice and professional, and the AsciiDoc rendering
is maybe even nicer than the HTML format. I'm not hating on PDF,
but for our purpose wonder if they're worth the weight.
* Am I worried to much about some extra files and some extra
disk space?
Thoughts?
DevNotes:
2021-02-17 ttyler: This job isn being suspended as it is being
filed to gather input on whether this change would be well
received.
Component: doc
Type: Feature