Summary:

• The 16.2 and 17.1 upgrade, update, and director guides, include a lot of references to different repositories, such as AUS, EUS, and e4s, e.g., rhel-8-for-x86_64-baseos-eus-rpms, rhel-8-for-x86_64-appstream-aus-rpms, etc.
  Any time a RHEL lifecycle ends, the repositories need to be updated in the docs. There are quite a few places in the docs where repositories are mentioned (see my notes). We need a strategy to update the current docs for each RHEL lifecycle milestone.

Goal:

• Determine how best to update the docs and maintain them while avoiding customer confusion. Some suggestions are:
  • Replace the repository type (e.g., AUS) with an attribute, e.g, rhel-8-for-x86_64-baseos-{repository}-rpms
  • Create a "source of truth" KCS to show which repos map to which RHEL version and their lifecycle expiration date.
  • Create tasks in Jira, much like the release tasks, to update the repositories in advance of the next RHEL lifecycle milestone (this will likely involve collaboration with reldel).

TimeBox:

• 1 week (unclear; it depends on how many discussions are needed)

Deliverables/Outcomes:

• Decision on a strategy to update the documentation.
• Jiras to get the work done.