Skip to content

Instantly share code, notes, and snippets.

Forked from hsbt/gist:7719305
Last active December 30, 2015 08:29
Show Gist options
  • Save sorah/7803201 to your computer and use it in GitHub Desktop.
Save sorah/7803201 to your computer and use it in GitHub Desktop.

Translation from

Proposal versioning after Ruby 2.1.0

Base Policy: follow Semantic Versioning basically


  • MAJOR: Increase when incompatible change (or some changes can't be releaed as MINOR) happened
  • MINOR: Increase at each December 25th; may be API incompatible
  • TEENY: Increase if doesn't match above 2 conditions; try to keep API compatibility
  • PATCHLEVEL: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)

Difference from knu's idea is: PATCHLEVEL keeps value across TEENY releases. Same with n0kada-san's idea in bugs.r-l.o.

In the expected user needs written in,

  1. Give me only security fixes (such as debian and heroku)
  2. Give me only bug and security fixes (normal Ruby users)
  3. Give me bug and security fixes, and some tiny new features and improvements (advanced users)
  4. Give me almost compatible (super advanced users)
  5. Don't care any compatibilities. (Ruby committers?)

TEENY releases satisfy (1) and (2). MINOR satisfies (3) and (4), and MAJOR satisfy (5).

We increase TEENY even if it'll be over 10. Assuming a {MAJOR}_{MINOR} version's maintaining term is about 2 years, we'll controll release cycle to be each 2 or 3 months. (note that this doesn't mean we don't release periodically)


  • trunk

We keep the above 2 branches. Keep using same {MAJOR}_{MINOR} branch across TEENY releases.

We add tags for each all releases.



We try to keep ABI compatibility among same {MAJOR}_{MINOR} release, so TEENY is fixed at 0.


TEENY を上げることで、アップデートのロビーイング効果を高めることができます。特にホスティング業界や保守的な業界の場合、2.0.0 というバージョンを採用することに消極なことがあり、2.0.1 と出すことで Ruby のパッチレベル運用について改めて説明する必要なく採用を進めることができます。

Copy link

olistik commented Jan 4, 2014

Agreed with @risen.

Copy link

ghost commented Jan 28, 2014

API incompatible should be change of MAJOR number, not MINOR number. API additions can be in MINOR or TEENY increments.

Copy link

Agreed wtith @risen.

Copy link

Agreed. This reads like pure lunacy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment