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

Update ferver link #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update ferver link #4

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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -311,7 +311,7 @@ Here are the cons:
#### Versioning Schemes
A pragmatic versioning scheme completes the overall API versioning strategy and addresses how to format the version number, when to upgrade and when to retire a version:

* We will base our approach on Semantic Versioning ([semver](http://semver.org/)) and Fear-Driven Versioning ([ferver](https://github.com/jonathanong/ferver)).
* We will base our approach on Semantic Versioning ([semver](http://semver.org/)) and Fear-Driven Versioning ([ferver](https://github.com/jaredly/ferver)).
* We will only use a Major and Minor version in the form `x.y`, where `x` >= 1 and represents the Major version number, and `y` >= 0 and represents the Minor version number.
* We never have a Major version of 0 because it makes the API appear unstable.
* There is no need to modify either the Major or Minor version for Non-Breaking changes.
Expand Down