New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path to version 1.0 #20451
Comments
This comment was marked as resolved.
This comment was marked as resolved.
I think we're doing just fine as-is. The versioning is driven by a very strong API contract ( |
That's ok, and also somewhat intentional. Because the things blocking 1.0 are things that must be fixed before we gain those remaining users who pay attention to the "1.0" signal.
That's not the standard for 1.0. What's needed for 1.0 is to decide various "one-way doors".
Promise/task is perhaps negotiable, but that doesn't really matter until the rest of the list is mostly complete. |
This post lists the conditions for declaring Nvim
v1.0
. This is not a roadmap; the project roadmap is here: https://neovim.io/roadmap/What is the plan for 1.0?
Stick to 0.x until the following conditions:
opts
param and return aDict
to ensure ability to augment them without breaking back-compat):help dev-api
:help dev-lua
vim.opt
/vim.opt_local
/vim.opt_global
--remote
docs: --remote alternatives #18414:checkhealth
reports use of deprecated RPC and Lua APIs.:lua foo.<tab>
completion should not suggest deprecated things. Lua: cmdline "vim.<tab>" completion: skip private and deprecated things #216601.0
Release 1.0 when we have fully-specified conventions for RPC API and Lua stdlib.
:help deprecated
, andvim.deprecate()
.2.0
:help api-contract
.nvim_xx
functions that alias allnvim_xx2
functions.nvim_xx2
names.nvim_exec
will aliasnvim_exec2
.nvim_exec2
will still exist but will be deprecated, and clients usingnvim_exec2
can easily migrate tonvim_exec
.The text was updated successfully, but these errors were encountered: