Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Versioning with SemVer #10

Closed
n1trux opened this issue Oct 12, 2019 · 2 comments
Closed

Versioning with SemVer #10

n1trux opened this issue Oct 12, 2019 · 2 comments

Comments

@n1trux
Copy link

n1trux commented Oct 12, 2019

IMHO, a specification should always have a revision format where application programmers and users alike can see which version of the specification the corresponding programs support.

I recommend SemVer. As a positive example I'd cite the Matrix.org spec.

Since editorconfig is a pretty small specification, the versioning should be pretty easy. Maybe just slap a v1.0 onto the spec if #2 and #8 are resolved? As there are already implementations of the spec which work somewhat this shouldn't be too risky.
@xuhdev
Copy link
Member

xuhdev commented Oct 12, 2019

I agree with you on using SemVer. Some details have been discussed in editorconfig/editorconfig#395

@xuhdev
Copy link
Member

xuhdev commented Oct 13, 2019

Since this is a duplication of editorconfig/editorconfig#395, I'm closing this now.

@xuhdev xuhdev closed this as completed Oct 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xuhdev @n1trux