docs: drop v1.0.0 from the roadmap; stay 0.x while foundations are pre-1.0#53
Merged
Conversation
…e-1.0
Re-version S6 from 1.0.0 to 0.5.0 ("Public release & launch") and rename
"Beyond 1.0" to "Beyond 0.5". Add a Versioning section explaining why Studio
stays in the 0.x range: Zig, the Native SDK, and the toolkit conformance
reference (itself 0.3.x) are all pre-1.0 and still make breaking changes, so a
1.0 would claim more stability than the stack it sits on. The S6 work is
unchanged — signed macOS app, Linux package, menu-bar monitor, docs, frozen
contract — only its version label.
ADR-0002's "post-1.0" references are left intact per the ADR immutability
policy; the platform decision (macOS-first, Windows later) is unchanged.
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
Drops
v1.0.0from the roadmap. Studio stays in the0.xrange until itsfoundations stabilize.
Why: Zig
0.16, the Native SDK0.4.1, and the toolkit — Studio's ownconformance reference, itself
0.3.x— are all pre-1.0 and still make breakingchanges (this codebase alone has absorbed Writergate, the
ArrayListAPI change,StringArrayHashMapremoval, andstd.fs.File→std.Io.File). A1.0wouldclaim more stability than the stack it sits on — and more than the reference
implementation Studio mirrors.
Changes
1.0.0→0.5.0, reframed "Public release & launch". The scope isunchanged — signed macOS app, Linux package, menu-bar monitor, docs,
automation-driven GUI test suite, frozen conformance contract — only the
version label.
carry breaking changes, always called out in release notes.
Not changed
The platform decision (macOS-first, Windows later) hasn't changed — only a
version anchor, which isn't a decision reversal.
Docs-only; CI runs the full matrix as a coherence check.