RETRO/SPIKE: List all actions that need to be automated

[heyselbi]

List all items that need to be automated.

Upstream to ODH automation:

• Text

ODH to RHODS automation:

• Text

PR process-related automation:

• text

Tag and Release automation:

• Create a tag automatically at the end of the sprint
• Create a release + release notes at the of the sprint
• Create a JIRA Story after feature freeze and after code freeze every sprint

GitHub Project Board:
Related Story issue

• When the sprint 1.X ends and a new sprint 1.X+1 starts, we want to update the Sprint tag in all of the issues that don't have the status of "Done" in Sprint 1.X.
• When pull request is linked, the Status should automatically change to "Under Review"

[Xaenalt]

Good candidate for automation would be end of each sprint a job to pull code from odh:main > odh:release > RHODS:main > RHODS:rhods-x.y and kick off the automatic builds, that would let us focus just on main branch for development

[danielezonca]

It is a "huge" ticket but I think we must find a solution to automate openshift-ci builds to inject the tag in the manifest as soon as we kick the release.
I would probably prefer to invest some time to migrate all pipeline out of openshift-ci so that we have a single release cycle but I don't know how big is this scope.

This is a related ticket of some manual activity to automate
https://issues.redhat.com/browse/RHOAIENG-860