Prepare for version 1.0
_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: 1. we have a full picture of what the RPC API and Lua APIs look like, this means conventions for: - function signatures (all RPC functions should have `opts` param and return a `Dict` to ensure ability to augment them without breaking back-compat) - naming conventions, `:help dev-api` `:help dev-lua` - https://github.com/neovim/neovim/issues/22287 - https://github.com/neovim/neovim/issues/19624 - https://github.com/neovim/neovim/issues/18585 - https://github.com/neovim/neovim/issues/11311 - https://github.com/neovim/neovim/issues/19918 2. Remove `vim.opt`/`vim.opt_local`/`vim.opt_global` 3. Redesign the "remote plugin" concept: https://github.com/neovim/neovim/issues/27949 4. Redesign `--remote` https://github.com/neovim/neovim/pull/18414 5. ✅ `:checkhealth` reports use of deprecated RPC and Lua APIs. 6. `:lua foo.<tab>` completion should not suggest deprecated things. - https://github.com/neovim/neovim/issues/21660 - https://github.com/neovim/neovim/issues/31376 # 1.0 Release 1.0 when we have fully-specified conventions for RPC API and Lua stdlib. - During 0.x, and continuing through 1.x, we will aggressively deprecate interfaces. This means: 1. they will be listed in `:help deprecated`, and 2. where possible they wi
Posted by justinmk on Oct 2, 2022, 4:52 PM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
Prepare for version 1.0
_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: 1. we have a full picture of what the RPC API and Lua APIs look like, this means conventions for: - function signatures (all RPC functions should have `opts` param and return a `Dict` to ensure ability to augment them without breaking back-compat) - naming conventions, `:help dev-api` `:help dev-lua` - https://github.com/neovim/neovim/issues/22287 - https://github.com/neovim/neovim/issues/19624 - https://github.com/neovim/neovim/issues/18585 - https://github.com/neovim/neovim/issues/11311 - https://github.com/neovim/neovim/issues/19918 2. Remove `vim.opt`/`vim.opt_local`/`vim.opt_global` 3. Redesign the "remote plugin" concept: https://github.com/neovim/neovim/issues/27949 4. Redesign `--remote` https://github.com/neovim/neovim/pull/18414 5. ✅ `:checkhealth` reports use of deprecated RPC and Lua APIs. 6. `:lua foo.<tab>` completion should not suggest deprecated things. - https://github.com/neovim/neovim/issues/21660 - https://github.com/neovim/neovim/issues/31376 # 1.0 Release 1.0 when we have fully-specified conventions for RPC API and Lua stdlib. - During 0.x, and continuing through 1.x, we will aggressively deprecate interfaces. This means: 1. they will be listed in `:help deprecated`, and 2. where possible they wi
Comments (0)
No comments yet. Start the discussion.