Upgrading Rails: The Non-Technical Parts
summary
Upgrading Rails focuses on organizational moves: claim that 50% of the battle is ownership, not code; audit gems and produce an unordered checklist, then set calendared milestones (examples: Halloween, Nov 15, Dec 15) and a deployment playbook with rollback and testing plans. Dual-boot lower envs, make CI boot the next Rails version, collect team-written regression tests, lean on Fast Ruby compatibility tables and next rails tooling, use AI to diff versions, and publish the plan (example: decomperie.com sprint poker).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:32Why Rails upgrades feel impossible
- 4:55Own the upgrade process
- 5:57Audit dependencies and plan
- 7:42Realistic milestones and deadlines
- 9:46Plan appendices
- 11:10Socialize plan across teams
- 13:23Empower the team
- 16:10Testing and deployment
- 18:57Success and failure after deploy
- 21:47Overcoming fear and first step
- 23:10Resources and closing
related talks
25mUpgrading Rails: Everyone can do it and here’s how
29mUpgrading Rails at Scale
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
36mRuby & Rails Versioning at Scale
39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0
36mRuby & Rails Versioning at Scale
35mTen years of Rails upgrades