Changes to "version" between 2018-07-03 20:17:00 and 2018-07-04 01:39:18

1
2
3
4
5
6
7
8


9
10
11
12
13
14
15
16
17
18
1
2
3
4
5
6


7
8
9
10
11
12
13
14
15
16
17
18






-
-
+
+










## # version:

Each plugin may carry its own version number:

    # version: 0.5

Which makes sense as features progress individually of the main application.
It's the whole point of plugin systems to provide independent functionality.
Which makes sense as features progress independly of the main application.
It's the whole point of plugin systems to encapsulate functionality.

  * Often it suffices to use MINOR.MAJOR schemes.

  * For larger plugins the more common SEMVER versioning might make sense
    still.

  * Patch versions etc. however shouldn't be part of the `version:` field.

Instead one can use [state:](wiki/state) or [support:](wiki/support) to expand
on the current code quality/completion.