-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
8
-
False
-
None
-
False
-
-
-
GitOps Crimson - Sprint 3256
Story (Required)
This story is for tracking the work required for release 1.11.4
- 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)
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<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
- clones
-
GITOPS-4523 Release v1.12.2 coordination
- Closed
- is cloned by
-
GITOPS-4596 Release v1.10.5 coordination
- Closed