Issue #19614 has been updated by austin (Austin Ziegler). This has been discussed and resolved before. See [15456#2](https://bugs.ruby-lang.org/issues/15456#note-2) for a note from one of the release maintainers specifically saying that Ruby is mostly a rolling release. There are flaws with Semantic Versioning as well, see [15456#5](https://bugs.ruby-lang.org/issues/15456#note-5). I also *do not use* full Semantic Versioning for any of my gems because it’s a deeply flawed system. The SemVer-ish decision was made in [#8835](https://bugs.ruby-lang.org/issues/8835) and [adopted with 2.1.0](https://www.ruby-lang.org/en/news/2013/12/21/ruby-version-policy-changes-wit...). I do not think that this is going to change. ---------------------------------------- Bug #19614: Adopt Semantic Versioning https://bugs.ruby-lang.org/issues/19614#change-102875 * Author: fulldecent (William Entriken) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Ruby was created in 1995. That's back when the UNIX timestamp was only 9 digits, before Nintendo 64, and before most people on Earth today were born. Since then, basically everybody else in the software industry has adopted Semantic Versioning. **Now it is time for Ruby to make this momentous change.** Not "almost SemVer". Not "sometimes SemVer". Actually "SemVer". This means: 1. Update the major version number (the FIRST part of the version string) with EVERY backwards incompatible change. 2. Follow every other rule published at https://semver.org/ 3. Tell everybody we are following SemVer. This issue is to promote the cause for SemVer and to change Ruby's release process to enter the 21st century. -- https://bugs.ruby-lang.org/