Skip to content

conduct: bring the 1.0 readiness page up to date - #192

Merged
Kinflou merged 2 commits into
mainfrom
docs/readiness-2026-11-16
Nov 15, 2026
Merged

Kinflou merged 2 commits into
mainfrom
docs/readiness-2026-11-16

Conversation

@Kinflou

@Kinflou Kinflou commented Nov 15, 2026

Copy link
Copy Markdown
Member

Refs #100

Brings docs/docs/conduct/readiness.md up to date; the date line is now 2026-11-16. Every issue state was checked with gh issue view first.

Marked built (closed): core#98, core#102, runtime#15, runtime#40, comline-typescript#75, comline-typescript#98, core#9, core#110. core#7 is also marked built (closed 2026-11-15, after the list in #100 was written).

Partly done, now described by what is left: cli#80, cli#82, docs#101 (licence part points to .github#5), docs#102, docs#103 (policy is in phases.md).

Fixed: runtime#17 is no longer described as undecided (strict by default, opt-in @open, decided 2026-10-20); the item now says what is left to implement. core#146 is noted as closed as not planned, with the work moved to core#268.

Added, in the existing sections: IR migrations (core#268) and the shared vocabulary (core#219) under "Interfaces that freeze"; offline and air-gapped use (core#227) and the runtime publishing issues labelled 1.0-blocker (runtime#115, comline-typescript#154, comline-rust#115) under "Distribution".

Not changed: the "Built (2026-11-01)" date on the extension API item, although core#120 and core#8 closed on 2026-10-31.

@Kinflou
Kinflou marked this pull request as ready for review November 15, 2026 17:38
@Kinflou
Kinflou merged commit cfe39db into main Nov 15, 2026
7 checks passed
@Kinflou
Kinflou deleted the docs/readiness-2026-11-16 branch November 17, 2026 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant