docs: add Rust modernization roadmap - #463
Conversation
dosubot
Bot
added
size:M
There was a problem hiding this comment.
Blocking: yes. Summary: This PR is not the place to add the detailed platform, release, or benchmark-report requirements discussed in the current comments. Please first clarify and agree on the intended rust-doc scope in issue #462, then update the PR;
until that discussion is complete, keep this PR in draft. Evidence: issue #462 lists the documentation hub and these details as separate follow-up work items; current head is 4c92b3a.
| - **Preview**: the component has documented installation and validation paths and is suitable for opt-in evaluation, but is not yet recommended as a production default. | ||
| - **Production-ready**: maintainers have documented support scope, compatibility, upgrades, rollback, operational limits, and release availability. | ||
|
|
||
| Every Rust-related page should state its maturity, owning repository or issue, supported platforms, known limitations, and the release containing the documented behavior. Planned behavior should be labeled **proposed**. |
There was a problem hiding this comment.
| - documenting an accepted proof of concept with reproducible commands; | ||
| - maintaining equivalent English and Chinese content. | ||
|
|
||
| Do not publish benchmark claims without the source revision, hardware, dataset, configuration, commands, and repeated results needed to reproduce them. |
There was a problem hiding this comment.
2 participants
What changed
Why
Issue #462 asks for a documentation hub that makes incremental Rust work discoverable without implying a wholesale rewrite or presenting proposals as shipped features.
Validation
git diff --checkhugo --minifywith the CI-pinned Hugo Extended 0.102.3 (157 EN pages, 156 CN pages)/docs/contribution-guidelines/rust-modernization/and/cn/docs/contribution-guidelines/rust-modernization/Follow-up before ready review
The repository contribution guide requests before/after screenshots. Because this is a new page, an after screenshot still needs to be attached to this draft PR before marking it ready.
Closes #462 only when maintainers consider the overview work sufficient; the issue's remaining templates and implementation-specific documentation can continue as child work.