3 ms·
Could be the time thing. Some of our apps at work have big-ish gem sets, but our ruby version upgrade cadence is much closer to update the version when the curr
by ufmace 4y ago
Could be the time thing. Some of our apps at work have big-ish gem sets, but our ruby version upgrade cadence is much closer to update the version when the current one is about to go out of support for security updates than grab the new hotness within a week of it being released.
- nevinera 4y agoOh yeah, that'll definitely do it. Our prior policy was to only adopt a version of rails when it's no longer the newest version of rails, and even that was enough to avoid most compatibility issues. We currently tend to adopt new versions of rails and ruby about a quarter after they are released (I wouldn't recommend "within a week" to any large project). It's worth noting that the reason there aren't a ton of compatibility issues 9 months after those things are released is _because_ of shops that perform the upgrades, find the issues, and report or solve them before then. The later you choose to go in the cycle, the less you'll be impacted, and the less you will contribute.