Release of v21.0.1-RC2

[rohit-nayak-ps]

Note

This release is scheduled for Tue 22 Oct 2024.
Release team: @vitessio/release

Important

Please do not edit the content of the Issue's body manually.
The vitess-releaser tool is managing and handling this issue.
You can however click on the check boxes to mark them as done/not done, and write comments.

Prerequisites (~2 weeks before)

• General prerequisites.
  • Be part of the Release team in the vitessio GitHub organization, here.
  • Be an admin of the planetscale/vitess-operator repository.
  • Have access to Vitess' Java repository and have it working locally, guide here.
  • Have vitessio/vitess and planetscale/vitess-operator cloned in the same parent directory.
• Notify the community on Slack.
• Make sure the release notes summary is prepared and clean.
• Make sure important Pull Requests are merged, list below.
  • [release-21.0] Bump to v21.0.1-SNAPSHOT after the v21.0.1-RC2 release #43
• Make sure release blocker items are closed, list below.

Pre-Release (~1-3 days before)

• Create Release PR. _{^{(We do this earlier to catch any issues in the tool and let CI run.)}}
  • [release-21.0] Release of v21.0.1-RC2 #41
• Update Cobra Docs.

Release (Tue 22 Oct)

• Merge the Release PR.
  • [release-21.0] Release of v21.0.1-RC2 #41
• Tag the release.
  • https://github.com/rohit-nayak-ps/vitess/releases/tag/v21.0.1-rc2
• Update release notes on main.
  • [main] Copy v21.0.1-RC2 release notes #42
• Go back to dev mode on the release branch.
  • [release-21.0] Bump to v21.0.1-SNAPSHOT after the v21.0.1-RC2 release #43
• Update the website documentation.
• Make sure the release is benchmarked by arewefastyet.
• Docker Images available on DockerHub.
• Check that the vttestserver image is pushed.
• Check that release artifacts were generated.

Post-Release (Tue 22 Oct)

• Notify the community on Slack for the new release.
• Twitter announcement.
• Remove bypass protection for release branch, if required.
• Close this Issue.