Quick Notes98 words
Hotfix path planning — quick notes
Hotfix path — quick notes
| Rule | Why |
|---|---|
| Branch from the released commit/tag | Isolates the fix from unreleased main work |
Merge back to main | Otherwise the next release reintroduces the bug |
| Same pipeline and gates | Emergencies are when gates matter most |
| Pre-agreed break-glass | Approvals belong to the resource owner — decide in advance |
| Record what was skipped | Makes the follow-up visible |
Trap: the most-tested hotfix failure is forgetting the merge back, so the defect returns at the next release.