0.11 is the stability candidate #336
Pinned
vyncint
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Ten releases in a month has been good for the crate and bad for anyone depending on it. 0.11 is where that stops.
Milestone
v0.11does three things: publishes a compatibility contract (#328 — what's promised, in which feature configurations), installs a semver gate on every pull request that can actually fail (#323, with a self-test proving it), and makes one breaking change —Screen::unsupported()returns a view instead of&[Arc<str>](#330, migration table in the issue). Nothing else is removed or moved behind a feature.wait_idle,Recording, the renderers and the_formethods stay exactly as they are.After 0.11.0, no promised item changes incompatibly before 1.0. The criteria 1.0 has to meet are in #335 — there is no date, deliberately.
If you contribute: API changes now need the
breakinglabel and the pasted semver diagnostics. The issues most useful right now are the enforcement ones (#323–#327) and the docs (#333, #334).If you use termlens outside this org: one of the 1.0 criteria is a real external project running tests on a release candidate. If that could be you, say so here.
All reactions