Versioning

Dan Rathbun

If you need adopt a version schema for your projects, you might want to understand how the Ruby Core itself handles versioning.

Semantic Versioning starting with Ruby 2.1.0

Dan Rathbun

And for information about typical Gem versioning:

RubyGems Rational Versioning

tt_su

@dan rathbun said:

Semantic Versioning starting with Ruby 2.1.0

Hallelujah! I'm glad they finally do this!

Jim

@dan rathbun said:

If you need adopt a version schema for your projects, you might want to understand how the Ruby Core itself handles versioning.

Semantic Versioning starting with Ruby 2.1.0

@unknownuser said:

Version Schema

MAJOR: increased when incompatible change which can’t be released in MINOR
    Reserved for special events
MINOR: increased every christmas, may be API incompatible
TEENY: security or bug fix which maintains API compatibility
    May be increased more than 10 (such as 2.1.11), and will be released every 2-3 months.
PATCH: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)

I didn't see where semver mentions bumping versions at Christmas, special events, or arbitrarily every 2-3 months. Is this versioning or marketing?

Maybe something was mangled in translation to English.

tt_su

Roadmap - Ruby - Ruby Issue Tracking System

Redmine

(bugs.ruby-lang.org)

Jim

Ah, so that just means yearly releases. So your encoding bugs might be fixed in 2.2.0 when release in December.

tt_su

It's still unclear what release they are scheduled for. Sometimes these things end up in new releases only - some times they backport the fixes.