This is an internal epic for tracking the action item defined during the team Agile Assessment.

Epic Goal

• Reduce the time and effort required to release the Red Hat WMCO

Why is this important?

• Reduce the time engineers spend on release work and thereby increase development velocity
• Reduce the time required to ship bug fixes and features to the customer
• Increase visibility into our release process for all stakeholders (QE, Docs, ProdSec, SP, PX)
• Give QE easy access to the most up-to-date operator and bundle images for their prep/testing

Scenarios

1. Implement/Improve automation of major release (x-stream) prep work
2. Implement/Improve automation of minor release (y- and z-streams) prep work
3. Improve documentation of release processes
4. Releases that have security fixes have a bit of additional work

Dependencies (internal and external)

1. ...

Acceptance Criteria

• All stories under this epic are closed out
• Succinct and clear checklists are created to outline the release process for x-, y-, and z- stream releases
• The amount of manual intervention to cut both major and minor releases is reduced
• Brew images with the latest code are available for QE (all supported WMCO versions)

Risks/Drawbacks

• ...

Open questions:

1. Does the scope include community operator release work?
2. How can our release process improve QE success?
3. How can we get the Greenwave CVP tests to spin up OVN hybrid clusters?
   1. This would remove the need to get CVP team to waive bundle image test each release (waiver requires QE and manager approval every time) and ease engineering’s manual testing
4. Can/should we make use of the automated erratas for z-streams?