ticdc: clarify rolling upgrade guidance

[lilin90]

What is changed, added or deleted? (Required)

Clarify the rolling-upgrade guidance for old-architecture TiCDC and compatibility for TiCDC.

Which TiDB version(s) do your changes apply to? (Required)

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)

What is the related PR or file link(s)?

• This PR is translated from: ticdc: clarify rolling upgrade guidance docs-cn#21496

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[gemini-code-assist]

Code Review

This pull request adds a placeholder file named temp.md. The review feedback identifies that the file lacks a proper top-level heading and contains placeholder text that does not meet documentation standards, providing a suggestion to include a relevant H1 heading in sentence case.

I am having trouble creating individual review comments. Click here to see my feedback.

temp.md (1)

The content of this file is placeholder text and does not align with the pull request's objective to clarify TiCDC rolling upgrade guidance. Additionally, the file lacks a top-level heading, which violates the Markdown style guide (MD041). Please replace this with the intended documentation content and ensure it starts with a proper H1 heading in sentence case.

# TiCDC rolling upgrade guidance

References

1. The first line in a file should be a top-level heading (MD041). ^(link)
2. Use sentence case for headings. ^(link)

[ti-chi-bot]

@wlwilliamx: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lilin90]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilin90

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [lilin90]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #22711.