Quick Notes136 words
Hotfix path planning — quick notes
Hotfix path — quick notes
| Rule | Why |
|---|---|
| Release-first | Branch from the maintained production release line, then PR the fix back |
| Main-first | PR the fix into main, then cherry-pick it into the current release branch |
| Keep both lines fixed | Port the exact change with a targeted cherry-pick and PR |
| Emergency validation | Preserve high-risk, low-cost checks; modify lower-risk, costly steps according to a predefined risk decision |
| Check bypass | Requires Administrator permission on the checked resource; the checks panel records who bypassed it |
| Incident governance | Predefine authorized responders and document high-impact actions |
Trap: a release-first fix that never reaches main can disappear from the next release.
Sources: https://learn.microsoft.com/en-us/azure/devops/repos/git/git-branching-guidance · https://learn.microsoft.com/en-us/devops/operate/how-microsoft-operates-devops · https://learn.microsoft.com/en-us/azure/devops/pipelines/process/approvals · https://learn.microsoft.com/en-us/azure/well-architected/operational-excellence/maturity-model · https://learn.microsoft.com/en-us/azure/well-architected/design-guides/incident-management