release: Don't require reviewers approval for the release PRs

[fidencio]

Anyone who has spent time doing releases has figured out that the process is time consuming, and one of the things that makes this more time consuming is having to find someone to review two PRs that are automatically generated and contain exactly what we expect from our scripts.

With this in mind, I really would like to ask whether we could have an agreement on the person who's handling the release merging the PRs without the need of the reviews, as long as the CIs and /test_kata_deploy are successful.

/cc @kata-containers/architecture-committee

[jodh-intel]

Thanks for raising this @fidencio. I'm sure we'd all prefer some manual reviews and acks but if the (global!) community are not able to react in a timely enough manner, we have to consider alternatives and this sounds like a pragmatic one.

Can you send a mail to the ML and add this to the AC meeting agenda so everyone is clear on this proposal:

If release PRs are not reviewed in a timely fashion (< 1 hour I'd say, but ideally even quicker), we are going to be forced to not require acks and automate the releases...

For reference, the release documentation is here:

• https://github.com/kata-containers/kata-containers/blob/main/docs/Release-Process.md
• https://github.com/kata-containers/community/wiki/Release-Team-Rota

/cc those who have been involved in release work in the past to get their input on the plan: @amshinde, @chavafg, @jcvenegas, @egernst, @bergwolf , @bpradipt.