Skip to content

docs: add query serving features to the release notes#10475

Merged
deepthi merged 3 commits intovitessio:mainfrom
planetscale:release-notes-14-main
Jun 20, 2022
Merged

docs: add query serving features to the release notes#10475
deepthi merged 3 commits intovitessio:mainfrom
planetscale:release-notes-14-main

Conversation

@systay
Copy link
Copy Markdown
Collaborator

@systay systay commented Jun 8, 2022

Description

This is a forward port of #10468

* docs: added to the release notes

Signed-off-by: Andres Taylor <andres@planetscale.com>

* Add name to static check workflow

Signed-off-by: Rohit Nayak <rohit@planetscale.com>

Co-authored-by: Rohit Nayak <rohit@planetscale.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jun 8, 2022

Review Checklist

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

General

  • Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
  • If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
  • If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.

Signed-off-by: Andres Taylor <andres@planetscale.com>
Copy link
Copy Markdown
Collaborator

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the gen4 changes need to be back ported to release-14.0

@deepthi
Copy link
Copy Markdown
Collaborator

deepthi commented Jun 14, 2022

The Gen4 related changes will need to be back ported to release-14.0 prior to GA.

Signed-off-by: Andres Taylor <andres@planetscale.com>
Copy link
Copy Markdown
Member

@frouioui frouioui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! We will need to port this to release-14.0 too, I see the original PR has less content than this one.

@deepthi deepthi merged commit bc2f459 into vitessio:main Jun 20, 2022
@deepthi deepthi deleted the release-notes-14-main branch June 20, 2022 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants