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.

Sign up for GitHub

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

Jump to bottom

[release-20.0] Release of v20.0.2 #16751

Merged
merged 3 commits into from
Sep 11, 2024
Merged

[release-20.0] Release of v20.0.2 #16751

merged 3 commits into from
Sep 11, 2024

Conversation

shlomi-noach
Copy link
Contributor

Includes the release notes and release commit for the v20.0.2 release. Once this PR is merged, we will be able to tag v20.0.2 on the merge commit.

@shlomi-noach
Unfreeze branch release-20.0
68ada16 
This commit was made automatically by the vitess-releaser tool.

See https://github.com/vitessio/vitess-releaser

Signed-off-by: Shlomi Noach <[email protected]>
@shlomi-noach
Addition of release notes
b816d83 
This commit was made automatically by the vitess-releaser tool.

See https://github.com/vitessio/vitess-releaser

Signed-off-by: Shlomi Noach <[email protected]>
@shlomi-noach
Update codebase for the v20.0.2 release
7a106a8 
This commit was made automatically by the vitess-releaser tool.

See https://github.com/vitessio/vitess-releaser

Signed-off-by: Shlomi Noach <[email protected]>
@shlomi-noach shlomi-noach added Component: General Changes throughout the code base Do Not Merge labels Sep 11, 2024
@vitess-bot vitess-bot
Copy link
Contributor

vitess-bot bot commented Sep 11, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Sep 11, 2024
@shlomi-noach shlomi-noach removed Do Not Merge NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Sep 11, 2024
@codecov Codecov
Copy link

codecov bot commented Sep 11, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.69%. Comparing base (7a42a88) to head (7a106a8).
Report is 1 commits behind head on release-20.0.

Additional details and impacted files 
@@               Coverage Diff                @@
##           release-20.0   #16751      +/-   ##
================================================
+ Coverage         68.65%   68.69%   +0.03%     
================================================
  Files              1541     1541              
  Lines            197937   197937              
================================================
+ Hits             135896   135975      +79     
+ Misses            62041    61962      -79

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot added this to the v20.0.2 milestone Sep 11, 2024
@shlomi-noach shlomi-noach merged commit 2592c59 into release-20.0 Sep 11, 2024
192 of 199 checks passed
@shlomi-noach shlomi-noach deleted the release-20.0-create-release-2 branch September 11, 2024 07:54
@shlomi-noach shlomi-noach mentioned this pull request Sep 11, 2024
Closed
22 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rohit-nayak-ps rohit-nayak-ps rohit-nayak-ps approved these changes

@systay systay systay approved these changes

@deepthi deepthi Awaiting requested review from deepthi deepthi is a code owner

@ajm188 ajm188 Awaiting requested review from ajm188 ajm188 is a code owner

@harshit-gangal harshit-gangal Awaiting requested review from harshit-gangal harshit-gangal is a code owner

@GuptaManan100 GuptaManan100 Awaiting requested review from GuptaManan100 GuptaManan100 is a code owner

@frouioui frouioui Awaiting requested review from frouioui frouioui is a code owner

@mattlord mattlord Awaiting requested review from mattlord mattlord is a code owner

Assignees
No one assigned
Labels
Component: General Changes throughout the code base Type: Release
Projects
None yet
Milestone
v20.0.2
Development

Successfully merging this pull request may close these issues.
3 participants
@shlomi-noach @systay @rohit-nayak-ps