From: "bkuhlmann (Brooke Kuhlmann) via ruby-core" Date: 2025-11-03T14:32:04+00:00 Subject: [ruby-core:123665] [Ruby Misc#21657] Question: Is Ruby 4.0 planned for December 2025 or later? Issue #21657 has been updated by bkuhlmann (Brooke Kuhlmann). **Jean**: Sorry, I didn't provide enough context to my original statement. Each year -- about ~2 months before Christmas when a new Ruby version drops -- I release a *patch* version of all my gems that accepts the current version and potential upcoming version. Example: ``` ruby # Assuming a Ruby 3.5.0 release. spec.required_ruby_version = ">= 3.4", "<= 3.5" ``` This gives the Ruby community some leeway (i.e. cross-over period) which supports the current Ruby version and the upcoming Ruby version. During this time, I'll test against both the old Ruby and the release candidates. Often, I'll report bugs here or bugs against the individual gems (which ever is most applicable). Once the new version of Ruby drops on Christmas (let's say Ruby 3.5.0 for this year). I'll release *major* versions for all my gems where the gemspec requirement is now: ``` ruby spec.required_ruby_version = "~> 3.5" ``` The reason I do this end-of-year dance each year stems from the following: - Ruby doesn't adhere to Semantic Versioning so I can't rely on each new version of Ruby causing maintenance grief. - Because each new Ruby can break functionality, I make sure to support the new syntax, drop the old syntax, etc. - I maintain ~50 gems (over ~15 years now), which are constantly kept up to date. I've also been trying to obtain funding for years and never get any so I can't maintain backwards compatibility because it's too costly (on my time) and would lead to extreme burnout. This is why I release a *major* version each year because I adhere to Semantic Versioning in order to communicate that a the major upgrade might require some work on those that upgrade. If people don't want to upgrade right away, they can still stay on the old version but that means they basically have a year to get their act together and upgrade before this process repeats again a year later. Again, this all stems from Ruby being chaotic with the version releases. If Ruby had more reliable version releases based on Semantic Versioning it means I could possible not have to release a major version of my own work each year with much more longer lived gem versions. This also echoes what, **Josef** has pointed out above as well: It's the randomness of Ruby versions that is the killer. This year is even worse because I can't even tell if Ruby will be a 3.5.0 or 4.0.0 release. ���� ---------------------------------------- Misc #21657: Question: Is Ruby 4.0 planned for December 2025 or later? https://bugs.ruby-lang.org/issues/21657#change-115047 * Author: dmitry.pogrebnoy (Dmitry Pogrebnoy) * Status: Feedback ---------------------------------------- Hello Ruby core team, I noticed that the first preview of Ruby 3.5 has been released, and at the same time there���s some talk in the community about Ruby 4.0 potentially arriving in December 2025. Could you please clarify what the current roadmap looks like? Is Ruby 4.0 already planned for this December, or is the next stable release still Ruby 3.5? Having a clear, public roadmap would really help library and tooling authors (like IDE vendors) prepare for upcoming versions and provide better support. Thank you! -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/