1
0
mirror of https://github.com/SpaceVim/SpaceVim.git synced 2025-02-03 03:00:04 +08:00

Update roadmap

This commit is contained in:
Shidong Wang 2018-12-27 23:06:41 +08:00
parent 5199be0265
commit 6efba6d3a0
4 changed files with 117 additions and 25 deletions

View File

@ -0,0 +1,39 @@
let s:self = {}
let s:self.begin = ''
let s:self.end = ''
let s:self.content_func = ''
let s:self.autoformat = 0
function! s:self._find_position() abort
let start = search(self.begin,'bwnc')
let end = search(self.end,'bnwc')
return sort([start, end], 'n')
endfunction
function! s:self.update(...) abort
let [start, end] = self._find_position()
if start != 0 && end != 0
if end - start > 1
exe (start + 1) . ',' . (end - 1) . 'delete'
endif
call append(start, call(self.content_func, a:000))
if self.autoformat
silent! Neoformat
endif
endif
endfunction
function! SpaceVim#api#dev#autodoc#get() abort
return deepcopy(s:self)
endfunction

View File

@ -6,23 +6,9 @@
" License: GPLv3
"=============================================================================
function! SpaceVim#dev#roadmap#updateCompletedItems() abort
let [start, end] = s:find_position()
if start != 0 && end != 0
if end - start > 1
exe (start + 1) . ',' . (end - 1) . 'delete'
endif
call append(start, s:generate_content())
silent! Neoformat
endif
endfunction
function! s:find_position() abort
let start = search('^<!-- SpaceVim roadmap completed items start -->$','bwnc')
let end = search('^<!-- SpaceVim roadmap completed items end -->$','bnwc')
return sort([start, end])
endfunction
let s:AUTODOC = SpaceVim#api#import('dev#autodoc')
let s:AUTODOC.begin = '^<!-- SpaceVim roadmap completed items start -->$'
let s:AUTODOC.end = '^<!-- SpaceVim roadmap completed items end -->$'
function! s:generate_content() abort
let content = ['## Completed',
@ -32,6 +18,13 @@ function! s:generate_content() abort
return content
endfunction
let s:AUTODOC.content_func = function('s:generate_content')
let s:AUTODOC.autoformat = 1
function! SpaceVim#dev#roadmap#updateCompletedItems() abort
call s:AUTODOC.update()
endfunction
function! s:get_milestones() abort
let milestones = github#api#issues#ListAllMilestones('SpaceVim', 'SpaceVim', 'closed', 'due_on', 'asc')
let line = []

View File

@ -1,5 +1,5 @@
---
title: "设计蓝图"
title: "设计蓝图"
description: "SpaceVim 设计蓝图和里程碑, 这决定了 SpaceVim 的开发方向和特性实现的优先顺序。"
lang: cn
---
@ -24,6 +24,7 @@ SpaceVim 的设计蓝图和[里程碑](https://github.com/SpaceVim/SpaceVim/mile
- [v0.7.0](#v070)
- [v0.8.0](#v080)
- [v0.9.0](#v090)
- [v1.0.0](#v100-1)
<!-- vim-markdown-toc -->
@ -33,11 +34,11 @@ SpaceVim 的设计蓝图和[里程碑](https://github.com/SpaceVim/SpaceVim/mile
## 版本说明
There are release milestones and meta milestones ("buckets").
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 `0.1.2`.
- 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 `0.1.2`.
- [todo](https://github.com/SpaceVim/SpaceVim/milestone/4) is a bucket for triaged tickets which should be on the roadmap but cannot yet be assigned to a concrete milestone.
- [unplanned](https://github.com/SpaceVim/SpaceVim/milestone/5) is a bucket for low-priority items or items lacking a feasible path to completion.
@ -49,7 +50,30 @@ There are release milestones and meta milestones ("buckets").
### [v0.1.0](https://github.com/SpaceVim/SpaceVim/milestone/1)
Will release 0.1 at 2017-01-27, as you know, it is the last day of this year in chinese.
the first public release of SpaceVim, and following feature will be implemented:
- Neovim-centric
- 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
- java
- js
- rust
- php
- go
- php
- lua
- perl
- python
- Extensive Neocomplete setup
- Central location for tags
- Lightweight simple status/tabline
- Premium color-schemes
release note: [v0.1.0](http://spacevim.org/SpaceVim-release-v0.1.0/)
@ -100,4 +124,10 @@ release note: [v0.8.0](http://spacevim.org/SpaceVim-release-v0.8.0/)
release note: [v0.9.0](http://spacevim.org/SpaceVim-release-v0.9.0/)
### [v1.0.0](https://github.com/SpaceVim/SpaceVim/milestone/13)
First stable release of SpaceVim
release note: [v1.0.0](http://spacevim.org/SpaceVim-release-v1.0.0/)
<!-- SpaceVim roadmap completed items end -->

View File

@ -1,5 +1,5 @@
---
title: "Roadmap"
title: "Roadmap"
description: "The roadmap and milestones define the project direction and priorities."
---
@ -23,6 +23,7 @@ The roadmap and [milestones](https://github.com/SpaceVim/SpaceVim/milestones) de
- [v0.7.0](#v070)
- [v0.8.0](#v080)
- [v0.9.0](#v090)
- [v1.0.0](#v100-1)
<!-- vim-markdown-toc -->
@ -32,11 +33,11 @@ The roadmap and [milestones](https://github.com/SpaceVim/SpaceVim/milestones) de
## Meta
There are release milestones and meta milestones ("buckets").
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 `0.1.2`.
- 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 `0.1.2`.
- [todo](https://github.com/SpaceVim/SpaceVim/milestone/4) is a bucket for triaged tickets which should be on the roadmap but cannot yet be assigned to a concrete milestone.
- [unplanned](https://github.com/SpaceVim/SpaceVim/milestone/5) is a bucket for low-priority items or items lacking a feasible path to completion.
@ -48,7 +49,30 @@ There are release milestones and meta milestones ("buckets").
### [v0.1.0](https://github.com/SpaceVim/SpaceVim/milestone/1)
Will release 0.1 at 2017-01-27, as you know, it is the last day of this year in chinese.
the first public release of SpaceVim, and following feature will be implemented:
- Neovim-centric
- 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
- java
- js
- rust
- php
- go
- php
- lua
- perl
- python
- Extensive Neocomplete setup
- Central location for tags
- Lightweight simple status/tabline
- Premium color-schemes
release note: [v0.1.0](http://spacevim.org/SpaceVim-release-v0.1.0/)
@ -99,4 +123,10 @@ release note: [v0.8.0](http://spacevim.org/SpaceVim-release-v0.8.0/)
release note: [v0.9.0](http://spacevim.org/SpaceVim-release-v0.9.0/)
### [v1.0.0](https://github.com/SpaceVim/SpaceVim/milestone/13)
First stable release of SpaceVim
release note: [v1.0.0](http://spacevim.org/SpaceVim-release-v1.0.0/)
<!-- SpaceVim roadmap completed items end -->