-
Notifications
You must be signed in to change notification settings - Fork 687
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
remove excessive clarifications as they apply to earlier GA releases #4549
Comments
@3pointer @overvenus PTAL, thanks |
@qiancai Please also take a look. |
Similar to my comment in 4552, here are my thoughts. @morgo, PTAL. Thanks. Background information: Possible solution: |
Thanks. @morgo Your suggestion has been accepted (see #4552 (comment)). @qiancai will open a pull request to close this issue, and she'll involve you as a reviewer if you want. |
/assign @qiancai |
Change Request
This repository is ONLY used to solve issues related to DOCS.
For other issues (related to TiDB, PD, etc), please move to other repositories.
Please answer the following questions before submitting your issue. Thanks!
See: https://docs.pingcap.com/tidb/dev/backup-and-restore-tool
There are a lot of clarifications which are only historically relevant. By keeping them here, they make it harder for first time readers to process the document:
For the use-case of backup+upgrade (where some of these restrictions apply), the documentation should be on the manual page for upgrading from the previous series (a new document under Maintain -> Upgrade).
The MySQL docs use the convention of removing the version-specific language in the GA that follows when it was introduced. See this example:
The text was updated successfully, but these errors were encountered: