request to follow SemVer/mention it in README about omniauth-saml

[md5]

@pravi Regarding the "request to follow", do you think that omniauth-saml hasn't followed SemVer for the most recent release?

[pravi]

@md5 I maintain gitlab package in debian. Gitlab wants omniauth-saml ~> 1.4.0 and that will break if I upload omniauth-saml 1.5.0. If gitlab is confident 1.5 will not break their code, they can confidently declare omniauth-saml ~> 1.4. But as things stand right now, there is no clear statement. Do you think its realistic for gitlab to check over 260 gems how each of their previous releases were? SemVer makes life easy for users of libraries and I think every library should follow it and make it easy for people to find that information.

[suprnova32]

@pravi what version of GitLab are you packaging? omniauth-saml was updated to 1.4.2 on version 8.4.4 and GitLab version 8.6 will make use of omniauth-saml 1.5.0.

You can see the commit for 1.4.2 here: gitlabhq/gitlabhq@ea7bdc7

and the commit 1.5.0 here: gitlabhq/gitlabhq@32ddf09

Please let us know where you think omniauth-saml has not followed the SemVer rules you mention.

[bufferoverflow]

I guess the thing @pravi likes to have is a clear commitment to semver principle and I agree with him we should mention this within the README.md to simplify life of software packagers and users.

I prepare a pull request for this.

[suprnova32]

if all it takes is a simple mention of commitment, then sure, let's commit.

[pravi]

Yes, a mention of commitment is all I need.