Three ways to plan an upgrade when your codebase is a patchwork
When your project has the same thing done three different ways, how do you bring everything up to date with a consistent approach?
In the latest episode of the No Compromises podcast, we discuss different strategies for tackling upgrades when parts of your codebase are multiple versions behind.
We walk through two main approaches and weigh the tradeoffs for both the developer doing the work and the person reviewing it.
Want help upgrading your Laravel project?
In the latest episode of the No Compromises podcast, we discuss different strategies for tackling upgrades when parts of your codebase are multiple versions behind.
We walk through two main approaches and weigh the tradeoffs for both the developer doing the work and the person reviewing it.
- (00:00) - Setting up the upgrade scenario
- (02:15) - Approach one: upgrade each area to current
- (04:00) - Why the reviewer's experience matters too
- (07:30) - A third approach neither one expected
- (09:00) - Silly bit
Want help upgrading your Laravel project?
