Bug 1476118 - [Docs][Package Manifest] Generate the Package Manifest for RHOSP 12 (post-GA)
Summary: [Docs][Package Manifest] Generate the Package Manifest for RHOSP 12 (post-GA)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 12.0 (Pike)
Assignee: Mikey Ariel
QA Contact: Lukas Ruzicka
URL:
Whiteboard: docs-accepted
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-28 05:32 UTC by Lucy Bopf
Modified: 2017-12-20 12:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 12:58:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lucy Bopf 2017-07-28 05:32:54 UTC
The Package Manifest document must be populated with the package information for the RHOSP 12 GA release.

Note: The Package Manifest updates can only be generated when ALL advisories included in the release have been shipped live.

Comment 3 Lucy Bopf 2017-12-14 07:13:53 UTC
Assigning to Mikey for review.

Mikey, I'm CCing on an email regarding the 'Package Designation' section of the Package Manifest, and we'll need to wait for a response there. But you should be able to go ahead with generating the chapter of tables for the GA release.

I have already added an entry in the 'Release Schedule' section, and added a placeholder chapter for RHOSP 12 GA.


For QA contact: Check particularly for any links that do not resolve, and any missing titles (the manifest-updater will mark these simply as 'CHANGEME').

Comment 7 Mikey Ariel 2017-12-20 12:02:36 UTC
Package designations incorporated into the document, peer review now in progress.

Comment 9 Mikey Ariel 2017-12-20 12:58:21 UTC
Package Manifest is now published on the Customer Portal:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/package_manifest/


Note You need to log in before you can comment on or make changes to this bug.