Description
Quoting editorconfig/editorconfig#395 (comment) :
- When the project started, there was only one core: the C core (initial commit 2011-10-22). The specification was whatever the C core accepted.
- The version number accepted by
editorconfig -b <ver>is the specification version.- At present, the specification version still matches the C core version.
- The
editorconfig-core-testversion lags behind the C core version because currently only the semver minor is used to indicate format changes. The C core uses the semver patch for bugfixes.If the above is correct (@xuhdev notes: This is correct), my revised request would be that the Board:
officially define the version number for
editorconfig -b/-v/--versionpurposes as theeditorconfig-core-testversion, so that the cores and plugins are decoupled from the specification (now that the specification is official per #361)bump
editorconfig-core-testtov0.13to mark this changeupdate the core tests (or accept a PR) here to permit major.minor version numbers (no patch)
officially permit plugins and cores to use version numbers that are different from
core-test.For example, the Vimscript core might respond to
-vwithEditorConfig Vimscript core v1.0.0 - Specification Version 0.13
Additionally:
- Defining the version of the specification as the version of editorconfig-core-test.
Should we make the changes proposed by the last 6 bullet points?
Please vote by commenting below: yes or no only. Voting will be closed at the end of April 9.
Discussion please goes to editorconfig/editorconfig#395
@editorconfig/board-member
cc @cxw42