[doc] zh release-2.1.6: split Improvements/Bug-fixes sections to mirror EN H3s#3775
Open
boluor wants to merge 2 commits into
Open
[doc] zh release-2.1.6: split Improvements/Bug-fixes sections to mirror EN H3s#3775boluor wants to merge 2 commits into
boluor wants to merge 2 commits into
Conversation
…or EN H3s The zh page consolidated several distinct EN sections into a single `### 存储管理` block with bold paragraph leads, so on-page navigation and section anchors did not line up with the EN page: Improvements: the zh `### 存储管理` block contained four EN subsections (Backup Recovery/CCR, Compaction, MOW, Storage Management) under bold paragraph titles `**备份恢复 / 跨集群同步**`, `**Compaction**`, `**Merge-on-Write**`, `**其他**`. Split them into proper H3s (`### 备份恢复 / CCR`, `### Compaction`, `### Merge-on-Write`, leaving the residual content under `### 存储管理`) so the heading set matches EN one-to-one. Bug fixes: zh `### 存储管理` actually held only the Backup & Recovery / CCR bullets — its content was wrong for the label. Rename it to `### 备份恢复 / CCR`, matching the EN heading. (EN's own `### Storage Management` bug-fixes heading is itself mislabeled — its bullets are all about routine load / group commit / data loading; zh already groups those correctly under `### 数据导入`, so no further restructure is needed.) No bullet content moved or rewritten. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… 2.1.6 The 6 `../../<path>` links in this release note can't resolve from the release-notes tree to the docs tree (they live in separate Docusaurus plugin instances), so Build Check flagged them as broken. Switch to absolute https://doris.apache.org/zh-CN/docs/2.1/... URLs to match the convention used in other release notes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The zh `release-2.1.6.md` page consolidated several distinct EN sections into a single `### 存储管理` block with bold paragraph leads, so on-page navigation and section anchors did not line up with the EN page.
Improvements section — the zh `### 存储管理` block contained four EN subsections (Backup Recovery / CCR, Compaction, MOW, Storage Management) under bold paragraph titles `备份恢复 / 跨集群同步`, `Compaction`, `Merge-on-Write`, `其他`. Split them into proper H3s (`### 备份恢复 / CCR`, `### Compaction`, `### Merge-on-Write`, leaving the residual content under `### 存储管理`) so the heading set matches EN one-to-one.
Bug fixes section — the zh `### 存储管理` block actually held only the Backup & Recovery / CCR bullets (its label was wrong for the content). Rename it to `### 备份恢复 / CCR`, matching the EN heading.
(Note: EN's own `### Storage Management` heading in Bug fixes is itself mislabeled — its bullets are all about routine load / group commit / data loading; zh already groups those correctly under `### 数据导入`, so that part of the structural mismatch is actually an EN bug, not a zh gap.)
No bullet content moved or rewritten — purely heading-level reorganisation.
Test plan