Automate release procedure

[akrejcir]

Create a script for creating github release, so we don't forget any of the steps.

For new major release:

• Create a new release-vX.Y branch from main.
• Create a tag vX.Y.Z on release-vX.Y branch.
• Create Github release from this tag. It's important to set target_commitish to release-vX.Y branch. CI uses it.
• Create an annotated tag api/vX.Y.Z pointing to the same commit as vX.Y.Z. This is needed to make the api submodule accessible.
• Post a PR to https://github.com/openshift/release repository to activate CI for the new release-vX.Y branch.

For new minor release:

• The same steps as above, but without creating a new branch and creating PR to https://github.com/openshift/release .

[codingben]

When that script (I believe CI job) will be executed? by a manual trigger, e.g. clicking on a button to execute CI job that will execute that script?

[akrejcir]

Deciding that is part of this issue.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[akrejcir]

/remove-lifecycle stale

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[akrejcir]

/remove-lifecycle stale

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[akrejcir]

/remove-lifecycle stale