Release of v17.0.0

[mattlord]

This release is scheduled for: Tuesday 27 June 2023.

Pre-Release

• Update the compatibility page
  • Update compatibility page for v17 website#1480
• Notify the community on Slack.
• Add the Backport to: release-17.0 label
• Make sure the release notes summary is prepared and clean
  • Prepare and clean summary docs for v17.0.0 #13363
• Move items in the release notes so that important things are on top
• Clean up deprecated flags
• Draft the blog post
  • https://docs.google.com/document/d/18f_p-3AG1RuiKb9nfskgFYLeg0doOYDQvdIrO9FafCc/edit#
• Review blog post
• Create a PR for the blog post on the website repository
  • https://github.com/planetscale/developer-education/issues/257
• Test the operator examples with the latest version of vitess-operator
• Make sure everyone in the release team has access to the Maven release website
• Prepare the x-posting of the blog post #13152
  • Vitess.io: Create the blog post announcing Vitess 17.0 GA website#1505
  • PlanetScale: https://github.com/planetscale/developer-education/issues/257
  • CNCF
• Backport PRs to verify
  • [release-17.0] Add RestorePosition and RestoredBackupTime as metrics to vttablet (#13339) #13358
  • [release-17.0] update link for reparenting guide (#13350) #13357
  • [release-17.0] bug: don't always wrap aggregation in coalesce (#13348) #13349
  • [release-17.0] bugfixes: collection of fixes to bugs found while fuzzing (#13332) #13346
  • [release-17.0] Bug fix: SQL queries erroring with message unknown aggregation random (#13330) #13335
  • [release-17.0] mysqlctl: Correctly encode database and table names (#13312) #13324
  • [release-17.0] Set the number of threads for release notes generation with a flag (#13273) #13278
  • Cherry-pick all pending PRs into release-17.0 #13364
• Must Fix issues
  • Handle inconsistent state error in query buffering #13333
  • Add RestorePosition and RestoredBackupTime as metrics to vttablet #13339
• Vitess Operator backport PRs to verify before release of operator
• Follow code-freeze/pre-release instructions from release documentation
  • Code freeze of release-17.0 #13368
• Create final release PRs
  • Release of v17.0.0 #13369
  • Forward port of release notes changes from v17.0.0 GA #13370

Release

• Follow the release instructions for release: here
  • Back to dev mode after v17.0.0 #13386
• Continue with the Java release following these instructions.
• On the Vitess website repository, make sure the docs are updates
  • Update website docs for the v17.0.0 GA release website#1510
  • Follow up of the v17.0.0 release with proper sha for local install website#1513
• Merge the 17.0.0 release notes on main
  • Forward port of release notes changes from v17.0.0 GA #13370
• Make sure arewefastyet benchmarks the new release (https://benchmark.vitess.io/status)
• Release the operator, v2.10.0.
  • Fix the operator tests to use the latest version after v17.0.0 release planetscale/vitess-operator#437
  • v2.10.0 release planetscale/vitess-operator#436
• Build and push the k8s images
  • Vitess: https://hub.docker.com/r/vitess/lite/tags
  • Vitess Operator: https://hub.docker.com/r/planetscale/vitess-operator/tags

Post-Release

• Notify the community on Slack.
• Make sure the Java release is available
• Make sure the blog post is published on:
  • PlanetScale: https://planetscale.com/blog/announcing-vitess-17
  • CNCF: https://www.cncf.io/blog/2023/06/27/announcing-vitess-17/
  • vitess.io: https://vitess.io/blog/2023-06-27-announcing-vitess-17/
• Benchmarking results
• Tweet both vitess release and operator release
• archive v14.0.0 ???

[frouioui]

This issue will close:

• v17.0.0 GA Code Freeze #12353
• v17.0.0 GA #12354

[mattlord]

I'm closing this as done! I will create a separate issue for the v14 deprecation.

[mattlord]

Follow-up issue for v14 EOL: #13418