The Release Train
Shipping to production across a fleet of clones: hotfix discipline, branch rules, and the verification habit of never trusting a green light you did not check yourself.
18 posts · ~78 min total reading
-
The Self-Updating Deploy Script That Has to Fail Once to Fix Itself
-
The False 200: When Removing a Binding Reveals Your Verification Was Lying
-
The release said LIVE. The code was not.
-
One Private Dependency, Five Different Failures
-
A var EDIT_DATABASE = false Sat in a Branch for 2.5 Years. Then We Shipped It.
-
The compile gate nobody wrote down
-
"Bamboo is broken" was wrong: a deploy that races the filesystem under CPU pressure
-
Hotfix branches need different rules than develop
-
The bug was wearing a trench coat
-
My hotfix skill learned that tags are a lie
-
Don't Trust the Green Deploy: Grep the Live File for Your Ticket Marker
-
A `?prototype=1` Flag and 23 Commits: Prototyping a Redesign in Production Code
-
187 Commits to Fix Four Bugs
-
The Real Release Started After the Tag
-
Env drift was the real bug
-
The SSL bug was easy. The bot traffic made it a day-long incident.
-
Six Production Releases in One Day: Anatomy of a Hotfix Train
-
Route a Change by Its Blast Radius, Not Its Size or Your Schedule