lifecycle: Update RELEASES_SELECTOR

[oshoval]

What this PR does / why we need it:
Remove old versions (keep 3 versions + release candid).
Update outdated version to use latest release of each minor.
Add missing releases.

Special notes for your reviewer:
Created this helper script, it will make this process less prone for mistakes
#1872

Release note:

None

[RamLavi]

Hey @oshoval thanks for the change,
This only changes the "short" lifecycle, that runs on every non-release PR
But we still have to update the "long" lifecycle, that runs over all the supported releases, and runs on every release PR.
Please consider updating that as well.

[oshoval]

Hey @oshoval thanks for the change, This only changes the "short" lifecycle, that runs on every non-release PR But we still have to update the "long" lifecycle, that runs over all the supported releases, and runs on every release PR. Please consider updating that as well.

Hi, I know and mentioned it as well on other PR today.
If you want please go ahead, atm I am focusing on short lifecyle.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[oshoval]

@oshoval: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-e2e-cnao-multus-dynamic-networks-functests 23c5c73 link true /test pull-e2e-cnao-multus-dynamic-networks-functests

#1871

[oshoval]

We should consider improving this flow, it can be semi automated
this way it will be less prone for mistakes

[oshoval]

/test pull-e2e-cnao-multus-dynamic-networks-functests

[oshoval]

@RamLavi
all lanes pass, do you want to review please ?
(sonar will be ignored for now)

[oshoval]

/lgtm
/approve

according review i dont see something blocking
we can always fix in case any thing needed anyhow

[kubevirt-bot]

@oshoval: you cannot LGTM your own PR.

In response to this:

/lgtm
/approve

according review i dont see something blocking
we can always fix in case any thing needed anyhow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oshoval

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [oshoval]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[RamLavi]

I wanted to suggest that we wait until the GA date so that we could remove another release from the list.
But I see that you already forced merge.

[oshoval]

Thanks, but there is no reason to wait for that, we can always remove that once it comes.
I pro unblocking stuff, small PRs, unless there is a reason to create dependencies.
Moreover, i kept here a window of 3 + RC (window of 4) + main, i think it is better than tight 3 + main.
We usually do that btw (length of the env var stayed the same, even that it was with non correct values).
Shrinking the window deserves its own PR and discussion, for sure not on this PR please.