[Discussion] Specifies the release specification

[AGDholo]

It is now in a period of rapid iteration, and releases can be managed later

Is your feature request related to a problem? Please describe. I noticed that we had made significant changes to the core code and whether we needed to do a large version iteration before merging into the master.

Describe the solution you'd like For instance #65 ,We might be able to release a version span similar to 1.1 -> 1.2, with a version control option like 1.1 -> 1.1.1 for daily fixes. Ref: Semantic Versioning 2.0.0

cc @lidangzzz @imtsuki

[imtsuki]

FYI: I noticed that the version number specified in package.json had never changed from the default (0.1.0) before. In #65 I picked 0.7.0 because 0.6.0 is the last version number that @lidangzzz has said on Twitter.

We can make use of lerna to do version number managing.

[AGDholo]

@imtsuki Is it necessary for us to use the GitHub release feature? Or wait for the 1.0 release, we are doing such management