larouxn left a comment (openstreetmap/openstreetmap-website#6333)
> Why do we need a consistent Ruby if we're supporting a range of versions?
For sure, it makes sense we can still support Ruby 3.3 and 3.2 as they're still
supported. At the same time I feel it makes most sense to have all contributors
and production be on the same version of Ruby for maximum consistency and
predictability between development and production.
> Why do I need to get pushed onto this version when I'm writing 3.2-compatible
> code?
Shouldn't we prefer people write code that adheres to the latest version of
Ruby both to prevent sooner need for maintenance given production runs latest
Ruby? Ruby 3.2 is EOL in 7 months and I suppose soon after it's EOL it will no
longer be supported in this repo. Meanwhile 3.4 has +2.5 years left.
([source](https://www.ruby-lang.org/en/downloads/branches/))
A bit contrived _but_ for example, when Ruby 4 comes out and strings are frozen
and production is upgraded to Ruby 4, assuming we don't merge
https://github.com/openstreetmap/openstreetmap-website/pull/5932 then writing
valid Ruby 3.3/3.4 code that modifies strings would break CI and production.
---
Ultimately, of course, we can close this PR if it's not wanted. :pray:
:bowing_man:
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6333#issuecomment-3201828983
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6333/c3201828...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
