Semantic versioning about ruby-jwt HOT 4 CLOSED

Sounds good. Just requires me to pay more attention to PR before doing
releases. Ideas on process that can be automated?

On Tue, May 6, 2014 at 5:00 PM, Peter Williams [email protected]:

The last release included an incompatible change to JWT's interface which
broke several of my projects. Any chance we could switch to semantic
versioning http://semver.org/ so that consumers of this API don't
unsuspectingly upgrade to incompatible versions?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37
.

Jeff Lindsay
http://progrium.com

from ruby-jwt.

Unfortunately, i have not found a good way to automate this. Sometimes an
"acceptance" test suite combined with CI can help. The idea being that if a
change to the library doesn't require a matching chance to the acceptance
suite then it is a patch version change; if it requires only an addition to
the acceptance suite the it is a minor version change; and if it requires a
modification of existing tests then it is a major version change. That is
not exactly automated but it does give one some hints about what should be
done.

Peter

On May 6, 2014 4:46 PM, "Jeff Lindsay" [email protected] wrote:

Sounds good. Just requires me to pay more attention to PR before doing
releases. Ideas on process that can be automated?

On Tue, May 6, 2014 at 5:00 PM, Peter Williams [email protected]:

The last release included an incompatible change to JWT's interface
which
broke several of my projects. Any chance we could switch to semantic
versioning http://semver.org/ so that consumers of this API don't
unsuspectingly upgrade to incompatible versions?

—
Reply to this email directly or view it on GitHub<
https://github.com/progrium/ruby-jwt/issues/37>
.

Jeff Lindsay
http://progrium.com

—
Reply to this email directly or view it on GitHub.

from ruby-jwt.

Alright, semantic versioning from here on out. 0.1.12 was yanked and 1.0.0 was released.

from ruby-jwt.

Sweet! Thanks a bunch.

On Wed, May 7, 2014 at 8:06 AM, Jeff Lindsay [email protected]:

Closed #37 #37.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37#event-118688794
.

from ruby-jwt.