Bump to v3.1.0-RC2

[mheon]

As the title says

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon

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 [mheon]

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

[mheon]

@cevich FYI, new branch here.

[mheon]

There's a test failure that seems consistent, but I have no idea how it could be related. Going to retry one more time before I look further.

[mheon]

Finally green.

@containers/podman-maintainers PTAL

[cevich]

Opened #9793 which should probably merge before this PR.

Also, @mheon does this mean I should start up daily cirrus-cron builds on this branch, and gut v3.0 .cirrus.yml down to minimal testing?

[mheon]

Yes to both.

[mheon]

I think we need to merge this as-is, though. I can't really rebase as the commit and tag are both signed.

[cevich]

I think we need to merge this as-is, though. I can't really rebase as the commit and tag are both signed.

Okay, the branch and tag testing might fail w/o that $DEST_BRANCH=v3.1 update, but should clear up after #9793 merges. I'm pretty sure I specified this in the release-process, so somebody isn't following the documentation 😄

I'll add v3.1 into the cron mix, and work on a PR to gut the v3.0 testing.

[mheon]

Eh, it's just an RC. We just need to get it right on Thursday for the final release.

[cevich]

Eh, it's just an RC

Yep, it's fine for an RC, I was just teasing.

I opened #9794 to dial-back the v3.0 testing, and a cirrus-cron job is setup for v3.1. Any failures should start showing up in tomorrow's report, otherwise "no news is good news".

[jwhonce]

LGTM

[TomSweeneyRedHat]

LGTM

[TomSweeneyRedHat]

/lgtm