Content-Length: 220462 | pFad | http://github.com/vitessio/vitess/issues/17898

94 Release of Vitess `v22.0.0` · Issue #17898 · vitessio/vitess · GitHub
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release of Vitess v22.0.0 #17898

Open
3 of 21 tasks
frouioui opened this issue Mar 3, 2025 · 0 comments
Open
3 of 21 tasks

Release of Vitess v22.0.0 #17898

frouioui opened this issue Mar 3, 2025 · 0 comments
Assignees
Labels
Component: General Changes throughout the code base Type: Release

Comments

@frouioui
Copy link
Member

frouioui commented Mar 3, 2025

Context

This issue tracks all the work for the v22.0.0 release, including RCs, code freeze, and GA. The version 2.15.0 of the vitess-operator will be released at the same time.

Key Dates (PDT)

Milestone Date
Code Freeze 01-04-2025
RC-1 08-04-2025
RC-2 (optional) 16-04-2025
GA 22-04-2025

Documentation and References


Task Breakdown

1. Pre-Code Freeze

  • Schedule Calendar Events: Set all meetings with the release team.
  • CLI Documentation: Re-generate and review for accuracy.
  • Deprecation Cleanup: Remove old deprecated flags and metrics.
  • Release Notes Review: Update and verify the release notes summary.
  • Vitess-Operator Release Notes: Write the release notes for the vitess-operator.
  • Team Permissions: Ensure all team members have the correct permissions.
  • Tooling Update: Update the vitess-releaser with recent bug reports and feature requests.

2. Code Freeze

  • Code Freeze: Ensure the new release-22.0 branch is frozen and main is bumped to v23.0.0-SNAPSHOT.

3. Pre-RC-1 Release

  • Draft Blog Post: Start drafting the release announcement blog post.
  • X-Post of the Blog Post: Notify organizations that usually x-post our announcement blog post.
  • CLI Documentation: Ensure the documentation is still up-to-date, re-generate if needed.
  • Release Notes Review: Re-verify the release notes summary.
  • Porting bug fixes: Keep a close eye on bug fixes and decide if they must be backported to release-22.0.

4. RC-1 Release

  • RC-1: Release v22.0.0-RC1 and vitess-operator v2.15.0-RC1.

5. Post-GA

  • Bug fixes: Keep a close eye to bug fixes merged on main and decide if they are worth a backport and an RC-2.
  • RC-2: If bug fixes are merged on release-22.0, start planning for a RC-2 release and repeat the tasks from step 3 and 4.
  • Final Blog Post: Finish the announcement blog post and notify organizations that cross-post it.
  • Release Notes Final Review: Make sure one last time that the release notes and changelog look correct.
  • CLI Documentation: Re-generate the documentation if needed, depending on recent merges to release-22.0.

6. GA

  • GA: Publish v22.0.0 and v2.15.0.
  • Announcements: Release the blog post and announce the new release on Slack and Twitter.
@frouioui frouioui self-assigned this Mar 3, 2025
@frouioui frouioui added Type: Release Component: General Changes throughout the code base labels Mar 3, 2025
@frouioui frouioui changed the title Release of v22.0.0 (tracking issue) Release of v22.0.0 Mar 5, 2025
@frouioui frouioui changed the title Release of v22.0.0 Release of Vitess v22.0.0 Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: General Changes throughout the code base Type: Release
Projects
None yet
Development

No branches or pull requests

1 participant








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/vitessio/vitess/issues/17898

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy