> Though ISO/IEC 30170:2012 doesn’t specify details of the Integer class, Ruby had two visible Integer classes: Fixnum and Bignum. Ruby 2.4 unifies them into Integer. All C extensions which touch the Fixnum or Bignum class need to be fixed.
Just as a data point, Ruby 2.3 is the version in the current Debian Stable (Stretch). Debian is currently in a release freeze with 2.5 in Buster, so it won't be this way for long.
> Stable is the current release and targets stable and well-tested software needs.[122] Stable is made by freezing Testing for a few months where bugs are fixed and packages with too many bugs are removed; then the resulting system is released as stable. It is updated only if major security or usability fixes are incorporated. This branch has an optional backports service that provides more recent versions of some software.
In what sense do they consider unmaintained software to be stable? What do they do if there's a security vulnerability in a feature that's been removed so there's nothing to backport? Stable as in dead.
depends on where you are going to, ideally you would go for 2.6. the vast majority of gems is compatible with 2.6 so it would mostly be fixing internal code.
the main change I remember would be the Fixnum/Bignum disappearing in favor of the Integer parent class [1][2][3] (which isn't hard to fix).
also if you are stuck on 2.3 you might have a lot of other issues too (like outdated gems).
Looking to upgrade an app from 2.3. What is the upgrade path? Can I just go to the latest version? Should I be watching for any regressions? Where would I find breaking changes?
