Bug 1463721 - Include Errata publication dates in 'Asynchronous Errata Updates' section of release notes
Summary: Include Errata publication dates in 'Asynchronous Errata Updates' section of ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Alex Dellapenta
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-21 15:01 UTC by Benjamin Holmes
Modified: 2017-06-22 21:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-22 21:50:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Benjamin Holmes 2017-06-21 15:01:38 UTC 
Document URL: 
https://docs.openshift.com/container-platform/<version>/release_notes/ocp_<version>_release_notes.html

Section Number and Name: 
Asynchronous Errata Updates

Describe the issue: 
We publish errata information to the OpenShift release notes. This includes a description of the errata, and a link. It is missing publication dates. Clients find this useful when referring to documentation.

Suggestions for improvement: 
Include errata publication dates in OpenShift Release Notes.

Additional information: 
Suggestion made by client to GPS member onsite
Comment 1 Benjamin Holmes 2017-06-21 17:08:46 UTC 
Currently actioning the item. Will raise a PR when done.
Comment 2 Vikram Goyal 2017-06-22 00:16:02 UTC 
@ashley @alex - FYI.
Comment 3 Alex Dellapenta 2017-06-22 21:50:15 UTC 
Addressed via the following PRs:

3.2: https://github.com/openshift/openshift-docs/pull/4644
3.3: https://github.com/openshift/openshift-docs/pull/4642
3.4: https://github.com/openshift/openshift-docs/pull/4640
3.5: https://github.com/openshift/openshift-docs/pull/4639

Already merged and published, so closing this out. Thanks for the feedback!
Note You need to log in before you can comment on or make changes to this bug.