docs: freeze the 2.0 scope and link the RTL limitation to #140#369
Merged
Conversation
Make the 2.0 boundary explicit: 2.0.0 ships exactly the packaging + hygiene set (modular split, legacy removal, release/publishing pipeline, compatibility tests, 1.9.x maintenance) and no further internal engineering is pulled in before GA. Further layout-class decomposition, abstraction cleanup, streaming, and optional performance work are deferred to the post-2.0 line and do not gate GA.
The support matrix already states text is laid out left-to-right with no bidi reordering or complex-script shaping; point that limitation at #140 so a reader evaluating the engine sees where full RTL / bidi support is tracked.
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.
Why
The 2.0 line is scoped as "packaging + internal hygiene, no new authoring API", but the ROADMAP
didn't state the boundary explicitly — and post-2.0 internal refactoring (layout-class
decomposition, etc.) had started landing on
2.0-devbefore GA. An explicit freeze keeps therelease cycle closing instead of the internals improving indefinitely. Separately, the RTL
limitation was documented but not linked to where it's tracked.
What
the packaging + hygiene set (modular split, legacy removal, release / publishing pipeline,
compatibility tests, 1.9.x maintenance — the last two were previously implicit) and that no
further internal engineering is pulled in before GA. Further layout decomposition, abstraction
cleanup, streaming, and optional perf work are explicitly deferred to the post-2.0 line (which
already exists as the "Next — post-2.0 engineering" section — no restructure needed).
link it to #140 so a reader sees where full
RTL / bidi support is tracked.
Docs-only; no build or runtime change.
Tests
CanonicalSurfaceGuardTest,DocumentationCoverageTest,PackageMapGuardTestgreen. The #140 linkresolves to the open RTL tracking issue.