Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-25243

Implement repo changes for 18.0 docs

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhos-18.0.z
    • documentation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • rhos-docs

      Goal: 

      • 18.0 and later - Remove specific repository names and redirect to https://access.redhat.com/support/policy/updates/openstack/platform/ as well as documenting the guidelines/considerations that Mike mentioned in his comment. Note that this might require creating a TOC in the Life Cycle page, which the PLM team would need to do (then we can deep-link or at least help customers find the right section on a long page).
        1. How should the lifecycle page be updated to make it a useful resource for customers? There is some information about repositories in the following sections:
      1. Extended Update Support Add-on

      1. Enhanced Extended Update Support Add-on

      1. KCS about EUS and Enhanced EUS
        Would it be useful to create a table showing which repositories are valid for RHOSO and RHEL, and when they expire? 
        1. We could emphasize that the customer needs to check their subscription.

      Acceptance Criteria:

      <-- Notes for defining Acceptance Criteria  - remove these notes before saving -->

      A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.

      • Verify X
      • Verify Y
      • Verify ...

              kgilliga@redhat.com Katie Gilligan
              kgilliga@redhat.com Katie Gilligan
              rhos-docs
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: