Skip to content

Adding Versioning Policy #35

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

Merged
merged 1 commit into from
Sep 13, 2019
Merged

Adding Versioning Policy #35

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
16 changes: 16 additions & 0 deletions VERSIONING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Versioning Policy

We use a three-part X.Y.Z (Major.Minor.Patch) versioning definition, as follows:

- X (Major) version changes are significant and expected to break backwards compatibility.
- Y (Minor) version changes are moderate changes. These include:
- Significant non-breaking feature additions.
- Any change to the version of a dependency.
- Possible backwards-incompatible changes. These changes will be noted and explained in detail in the release notes.
- Z (Patch) version changes are small changes. These changes will not break backwards compatibility.
- Z releases will also include warning of upcoming breaking changes, whenever possible.

## Beta Releases

Versions with a zero major version (0.Y.Z) are considered to be beta releases.
In beta releases, a Y-change may involve significant API changes.