-
Notifications
You must be signed in to change notification settings - Fork 688
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
releases: add TiDB 7.1.0 release notes (stable version) #13484
Conversation
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
…uster upgrade Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM for performance test part. |
- update enterprise link - remove tw id and dup label - fix format, anchor, typo - fix contributor id of TiCDC DDL replication - update the order of Improvements/TiDB/ issue 42227 - add experimental label for DDl distributed parallel execution framework - contributors: remove asjdf because the PR is not merged into release-7.1; add First-time contributor label for yujiarista Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Co-authored-by: xixirangrang <hfxsd@hotmail.com>
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 33484a5
|
In response to a cherrypick label: new pull request created to branch |
What is changed, added or deleted? (Required)
releases: add TiDB 7.1.0 release notes
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?