There are release milestones and meta milestones (“buckets”).
- Version-number milestones (0.1, 0.2, 0.3, …) assign issues to production releases.
- The nearest upcoming version is assigned a target date.
- Low-risk fixes in the current branch are first committed to the stable branch, then merged to master. For example, if the current stable release is
0.1.1 and a bug-fix is assigned to the
0.2 milestone, it does not mean users need to wait until 0.2 to get the fix. The patch will be committed to the stable branch and released in
- todo is a bucket for triaged tickets which should be on the roadmap but cannot yet be assigned to a concrete milestone.
- unplanned is a bucket for low-priority items or items lacking a feasible path to completion.
the first public release of SpaceVim, and following feature will be implemented:
- Modular configuration
- multiple leader mode
- Lazy-load 90% of plugins with dein.vim
- Robust, yet light weight
- Unite centric work-flow
- Awesome ui
- Language specific mode, code completion, syntax check, etc.
- c family
- Extensive Neocomplete setup
- Central location for tags
- Lightweight simple status/tabline
- Premium color-schemes
release note: v0.1.0
- Many language support
- Improve default layer
- finish document
release note: v0.2.0
- SpaceVim api
- plugin manager ui ( for dein)
release note: v0.3.0
features need to be implemented just after v0.3.0 has been released.
release note: v0.3.1
release note: v0.4.0
release note: v0.5.0
release note: v0.6.0
- Improve all the lang#* layers
release note: v0.7.0
release note: v0.8.0
release note: v0.9.0
First stable release of SpaceVim
release note: v1.0.0