The Past, Present, and Future of Rails at GitHub

on YouTube ↗38m

" summary

GitHub upgrades from Rails 3.2 to 5.2, paying down a decade of fork-driven debt that once caused ~2,500 test failures and left the codebase 10 years behind. The team uses a dual-booting approach, hacks bundler to support multiple Gemfiles, runs hubot CI checks, and organizes work with projects and issues. A four-engineer full-time push deploys Rails 4.2 and later 5.2 with zero downtime, and afterward GitHub lands 75 pull requests into Rails 6 and extracts multiple-database support into upstream Rails.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 2:16the rails core team
3. 25:25test new releases of rails in the beta or release candidate phase
4. 27:18apply a security patch
5. 30:33adding multiple databases to an application

" related talks

• 38mThe Past, Present and Future of Rails at GitHubEileen M Uchitelle · Balkan Ruby 2019
• 42mThe Past, Present, and Future of Rails at GitHubEileen M Uchitelle · Ruby on Ice 2019
• 40mThe Past, Present, and Future of Rails at GitHubEileen M Uchitelle · RailsConf 2019
• 06mGitHub - Tal SafranTal Safran · RailsConf 2018
• 33mUpgrading a big application to Rails 5Rafael Mendonça França · RailsConf 2017
• 22mRiding Rails for decadesRafael Mendonça França · RubyConf Colombia 2016
• 31mBuilding new on top of old: the argument for simplicitySam Lambert · The Lead Developer 2016
• 36mRuby & Rails Versioning at ScaleGeorge Ma · RailsConf 2024