Skip to content

Vitess Release v21 Tracking Issue #16795

Closed
@rohit-nayak-ps

Description

Feature Description

This is a tracking issue for the upcoming release of Vitess 21. Aims to hos pending todos and further document the process.
21.0 Team: Rohit (Release Manager), Shlomi (Previous RM), Florent (Release Wizard and Next RM)
Clarification: The vitess-releaser is automates most of the release process including creating release-related PRs. This PR is a complement to it, for tracking progress and ongoing issues/todos, but it will not be used by the tool.

Before/Post GA

  • Check benchmarks run after Florent is done with current benchmarks work
  • Update Summary doc with changes to public API (GRPC / protos) in v21 wrt v20
  • CNCF Blog Post final Google Docs (by 18 Oct)
  • Summary verification (by Deepthi by 25 Oct)
  • Regenerate cobra docs (Oct 29)
  • Florent to validate that benchmarks are running on the v21 tag once he is done with his current development there
  • Florent to post in twitter
  • Team: needs to update/decide on the GRPC changes to be added to the summary ([Direct PR][release-21.0] Add RPC changes segment in the summary doc #17034) and then merge once done
  • Rohit: PR to lift code freeze and merge all approved release-21.0 PRs
  • Rohit: announce EOL for v18. Document and remove references to it "everywhere"

Backports for v21 RC2

Todos

  • Vitess releaser: fix docker link
  • During RC-2 update the code examples of the vtop release-2.14 branch to use rc2
  • Update vitess-releaser for cobradocs generation: pre-release
  • Update vitess-releaser checklist for vttestserver image generation: post-release
  • Update vitess-releaser checklist for removing Bypass Protection from vitess repo: post-release
  • Add to vitess-releaser checklist for verifying that /releases artifacts are created: post-release
  • Add to vitess-releaser checklist for GA to message CNCF about blog post (already there?)
  • Announce on OSS Slack, upcoming code freeze and release two weeks before code freeze: https://vitess.slack.com/archives/C0PQY0PTK/p1727123807991129
  • Vitess Releaser changes for v21 Initial set of changes for v21 release vitess-releaser#112
  • Announcement on OSS Slack two days before code freeze
  • Deepthi to check release notes Oct 2nd
  • CNCF Blog Post initial

(Potential) Backports for v21 RC1

Issues to Merge before RC code freeze

Stuff to add to summary.md

  • atomic transactions
  • mysql 8.4 support

Release artifacts

The goal of a Vitess release is to generate the following artifacts for every release including GA and intermediate RCs (and subsequent patches).

  1. A git hash that marks the commit at which the release is cut.
  2. Vitess binary and operator Images should be pushed to Docker Hub: should be visible at https://hub.docker.com/u/vitess like https://hub.docker.com/r/vitess/lite/tags?name=v20
  3. Java packages to be pushed to Maven/SonaType
  4. Notifications to Twitter/Slack
  5. CNCF Blog post
  6. Updated vitess.io Website documentation

Prep Work

  • Monitor PRs that need to go into the release from a few days before
  • Validate release notes

Dates

Tentative dates, pending schedule alignment:

  • Before October 8: Pre-Requisites for a release (check environment, check GH rights, check release notes, etc)
  • Tuesday 8 October: release-21.0 Code Freeze (Zoom Meeting needed)
  • Between the 8th and 14h: v21.0.0 RC-1 Pre-Requisites
  • Monday 14 October: v21.0.0 RC-1 Pre-Release (Zoom Meeting needed)
  • Tuesday 15 October: v21.0.0 RC-1 Release (Zoom Meeting needed)
  • Monday 21 October: v21.0.0 RC-2 Pre-Release (optional) (Zoom Meeting needed)
  • Tuesday 22 October: v21.0.0 RC-2 Release (optional) (Zoom Meeting needed)
  • Between the 22nd and 28h: v21.0.0 GA Pre-Requisites
  • Monday 28 October: v21.0.0 GA Pre-Release (Zoom Meeting needed)
  • Tuesday 29 October: v21.0.0 GA Release (Zoom Meeting needed)

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions