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

[main] Copy v19.0.5 release notes #16455

Merged
merged 1 commit into from
Jul 23, 2024
Merged

[main] Copy v19.0.5 release notes #16455

merged 1 commit into from
Jul 23, 2024

Conversation

systay
Copy link
Collaborator

@systay systay commented Jul 23, 2024

This Pull Request copies the release notes found on release-19.0 to keep release notes up-to-date after the v19.0.5 release.

@systay
Copy release notes from release-19.0 into main
270b4c5 
This commit was made automatically by the vitess-releaser tool.

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

Signed-off-by: Andres Taylor <andres@planetscale.com>
@systay systay requested a review from deepthi as a code owner July 23, 2024 07:39
@systay systay added Component: General Changes throughout the code base Type: Release labels Jul 23, 2024
@systay systay mentioned this pull request Jul 23, 2024
Closed
23 tasks
@vitess-bot vitess-bot
Copy link
Contributor

vitess-bot bot commented Jul 23, 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 Jul 23, 2024
@systay systay removed 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 Jul 23, 2024
@systay systay merged commit 2637a88 into main Jul 23, 2024
11 checks passed
@systay systay deleted the main-release-notes-main-5 branch July 23, 2024 07:39
@github-actions github-actions bot added this to the v21.0.0 milestone Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

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

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

Successfully merging this pull request may close these issues.
1 participant
@systay