Milestones
List view
Loose ends from 0.1.0, plus possibly one additional platform — which one is undecided, so no platform epic carries this milestone yet. The test for putting something here: would we hold the 0.2.0 release for it? If we would ship without it, it belongs at no:milestone instead. This is not a backlog — there is deliberately no Future or Backlog milestone, because that would be a second way to say uncommitted. Deliberately undated. Per the milestone convention, a due date is set only where an external commitment exists; 0.1.0 and 1.0.0 carry dates because both are stated publicly on the website. No date for 0.2.0 has been published.
No due date•0/18 issues closedThe commitment that the public API is stable. After 1.0.0, a breaking change costs a major version. Committed for release by the end of 2026. The 0.x releases in between add platform support and answer integration feedback; each is milestoned as it is planned. This milestone holds only what must be settled before the stability commitment itself: API review, and any breaking change that beta feedback shows is needed.
Due by December 31, 2026•1/1 issues closedFirst public release. Production quality and thoroughly tested, supporting a limited set of platforms. Beta describes the breadth of platform coverage and the absence of field integration so far, not the maturity of the code. The public API is believed stable; if integration feedback shows a problem with it, we reserve the right to change it, which is what the 0.x series is for.
Due by August 31, 2026•288/288 issues closed