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

doc: document versioning policy #42

Closed
wants to merge 1 commit into from
Closed

doc: document versioning policy #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions doc/VERSIONING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Versioning

When we reach 1.0, we will just adhere to [semantic
versioning](http://semver.org/) strictly, but semver says nothing about
versions `<1.0.0`. Thus we extend semver's rules applying them to these
versions this way: in `0.minor.patch` scheme `minor` acts as a major semver
version and `patch` as both minor and patch, regardless of whether a change is
a feature or a bugfix.

Accordingly, if labels named `semver-major` or `semver-minor` are added to any
issue or pull request before we have released `v1.0.0`, they actually assume
minor and patch subversions.