The Release Mainline
Each release has a “mainline” branch
- This might be /main, but might not be
- Low risk activities can be performed directly on the mainline
Multiple releases can be underway at the same time
- Use separate mainline branches
The mainline should be available as much as possible to avoid blocking progress
- Use “stabilization” sub-branches to allow the mainline to remain open