-
Task
-
Resolution: Done
-
Undefined
-
1.9.1
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 242
Story (Required)
This is a story to track all the release activities. The owner of the story should act as a release manager and drive the release.
Background (Required)
Patch release for v1.9.1
Out of scope
Fixing the issues for v1.9.1
Approach (Required)
Use https://spaces.redhat.com/pages/viewpage.action?pageId=133570094 for instructions
Dependencies
https://issues.redhat.com/projects/GITOPS/versions/12407286
Acceptance Criteria (Mandatory)
See the Release Manager Guide for more information
- Complete Prerequisites (if necessary)
- Make a story in JIRA for tracking release activities (see below)
- Create a new errata advisory
- Update Component Matrix in Confluence
- Create the build pipeline
- Update Argo CD version in argocd-operator repo (if necessary), i.e. if argocd version upgrade
- Update gitops-operator repo (if necessary), i.e. if argocd-operator or argocd version in argocd-operator was upgraded
- Trigger build
- Sanity Checks
- Attach builds to the errata release advisory
- Attach Jira issues to the errata release advisory
- Move the advisories into QE state & get QE Approval
- Get docs team approval on advisories
- Tag release branches in midstream and gitops-operator repose
- Get the binaries signed (if there is an RPM (KAM) advisory)