This story covers documenting the release process for minor releases from start to QE hand-off. This will allow us to highlight any differences in the major vs minor release processes and better communicate release status to all stakeholders.

For each step, call out

• Manual or automated process?
• Can it be done in parallel with any other steps?
• Requires action from external teams? If so, which ones/who?

List out every step of the process from the dev side so any team member to cut a release from start to finish without any background knowledge. Assume reader has proper accesses already. Outline what is needed in:

• WMCO Github (upstream)
• gerrit code review (midstream)
• dist-git/cgit (downstream)
• Gitlab CEE
• Errata tool
• Comet
• Jira/Jenkins/Bugzilla
• QE/Docs/ProdSec communication
• Any dev testing/validation

Releasing the Red Hat WMCO and CPaaS Cheat Sheet can be used as inspiration.

Acceptance Criteria:

• The output of this story should be a list that documents every step of the process in a succinct workflow (markdown template)
• list formatted so that it can be copy/pasted onto a the release tracking Jira ticket and steps checked off as we make progress