Story (Required)

• As a Release engineer trying to make a z stream release for 1.15, I want to release the upstream gitops-operator, so that I can use that for the downstream build that gets released to the customer.

Background and Approach (Required)

• Update the commit id of argocd-operator in go.mod file.
• Update the commit id of the rollouts-manager in go.mod file.
• Create a PR and if the changes look good, merge the PR.
• Refer the commit id in the midstream repo.

  Out of Scope

  *

Dependencies

Acceptance Criteria (Mandatory)

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.