Story (Required)

As a release engineer, releasing OpenShift GitOps 1.18.0, I want the the PLM Product Ops page be updated with the EOL dates and maintenance details so that customers are made aware of the lifecycle dates of OpenShift GitOps.

Create a JIRA ticket under PLM Product Ops

Out of scope

NA

Approach (Required)

1. Create a JIRA ticket under PLM Product Ops with the title "Update OpenShift GitOps lifecycle page for 1.18.0"
2. Provide the following details

• Release Date
• Supported OCP versions (eg. 4.12-4.19)
• Full support end date (eg: for 1.17.0, it is with release of 1.18.0 N+1)
• Maintenance support date ( eg. for 1.17.0, it is with release of 1.20.0 N+3
  3. File a 'life cycle update ticket using https://docs.google.com/forms/d/e/1FAIpQLSdX2lc4n3AT7rHyth_lNpZAJ-7JMsCHiyfDnQJC92jS2eYQOA/viewform"
  4. Example tickets
  PLMCORE-12621
  PLMCORE-12277

Dependencies

The release should have been completed and the errata should be in SHIPPED_LIVE state.

Acceptance Criteria (Mandatory)

The product ops page is updated with the right information
https://access.redhat.com/product-life-cycles
https://access.redhat.com/product-life-cycles?product=Red%20Hat%20OpenShift%20GitOps

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met