Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-811

[OCM-UI] candidate 4.y.z on the release page may link non-existent release notes

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • False
    • True

      The release notes for 4.y.z are published around when the errata is published, which also triggers 4.y.z's inclusion in fast-4.y and similar channels. Release page candidate entries like 4.9.5 currently link to a release note entry, but before 4.9.5's errata is published, that entry won't exist. Possible mitigations:

      1. Remove the release-notes link for all candidate entries. This will never link to a non-existent location, and the lack-of-link for post-errata releases is mitigated by "user looks a few pixels up and sees the same 4.y.z with a release-notes link under fast-4.y".

      2. Do something clever in the release page logic like "only link the candidate entry to release notes when you have the same 4.y.z as the tip of candidate-4.y and fast-4.y".

      3. Keep the current behavior. Customers are unlikely to click through to release notes for the candidate release, and if they do, a bit of scrolling around when they land will remind them that the candidate release isn't GA yet.

      4. Other?

      I'm personally agnostic between 1 and 2, and prefer both of them to 3.

            Unassigned Unassigned
            trking W. Trevor King
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: