[docs] reorganize 2.0.0 feature documentation structure#994
Merged
[docs] reorganize 2.0.0 feature documentation structure#994
Conversation
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
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.
What is the purpose of the change
Background/Problem:
Currently, feature documentation for version 2.0.0 is scattered across multiple dev-1.19.0-* directories, making it difficult to manage and maintain. The fragmented structure reduces documentation discoverability and maintenance efficiency.
Purpose of Change:
To address this problem, this PR consolidates all design documents, requirement documents, and test documents from various dev-1.19.0-* directories into a unified docs/dev-2.0.0/ directory structure with proper subdirectories for design, requirements, features, and testing.
Value/Impact:
After the change, all 2.0.0 related documentation is organized in one centralized location, improving documentation discoverability, maintenance efficiency, and providing clear version separation.
Related issues/PRs
Related issues: close #993
Related pr:none
Brief change log
Checklist