DM: Remove broken docs links#22840
Conversation
ti-chi-bot
Bot
added
missing-translation-status
|
Maybe more of the v5.x and earlier things for DM should be removed? |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request removes outdated links to archived DM documentation and updates the note regarding DM versioning history. A suggestion was made to further simplify the explanation of the version jump from v2.0 to v5.3 to improve readability and reduce wordiness in accordance with the style guide.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
|
||
| Before v5.4, the DM documentation is independent of the TiDB documentation. To access these earlier versions of the DM documentation, click one of the following links: | ||
|
|
||
| - [DM v5.3 documentation](https://docs-archive.pingcap.com/tidb-data-migration/v5.3/) |
There was a problem hiding this comment.
These links are broken now because of a bug in the website-docs repo. Let me try fixing it.
fix DM archive URL resolution by qiancai · Pull Request #698 · pingcap/website-docs
There was a problem hiding this comment.
@dveeden FYI, these broken links are fixed now. Could we revert the removal of these lines in this PR?
[LGTM Timeline notifier]Timeline:
|
hfxsd
added
translation/no-need
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
In response to a cherrypick label: new pull request created to branch |
4 participants
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?