24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# Roadmap From 1.0.0-beta To Stable
|
|
|
|
## Stable Criteria
|
|
|
|
Slovo reaches stable `1.0.0` only after:
|
|
|
|
- compatibility rules are documented and exercised across multiple beta releases
|
|
- formatter and diagnostics schemas are frozen for promoted features
|
|
- `lib/std` has clear API stability tiers
|
|
- package/workspace behavior has deterministic version and dependency policy
|
|
- conformance tests cover normal user projects, not only narrow fixtures
|
|
- benchmark publication remains repeatable without becoming a performance claim
|
|
|
|
## Recommended Sequence
|
|
|
|
1. Harden monorepo release tooling, clean docs, and public install/build flow.
|
|
2. Stabilize `lib/std` module boundaries and document beta-vs-stable APIs.
|
|
3. Broaden numeric completeness with explicit `f32` and additional integer
|
|
policy where needed.
|
|
4. Improve collection and string breadth without exposing unstable ABI details.
|
|
5. Expand package/workspace discipline before remote registry work.
|
|
6. Add editor-facing diagnostics and generated documentation improvements.
|
|
7. Freeze migration/deprecation policy and cut stable only after beta feedback.
|