How does a branching strategy influence release cycles?

• A. It has no impact on CI gates
• B. Plan for feature branches, releases, and hotfixes
• C. It only affects code formatting
• D. It dictates code languages used

Answer: (B)

A branching strategy directly shapes release cycles by organizing how work is prepared for delivery. By planning for feature branches, a development line, a release branch, and hotfix branches, you create a predictable path from active development to production. Feature branches let teams work on new functionality without destabilizing the main line. When a set of features is ready, a release branch is created to stabilize and test those changes together before they go live. If a critical issue is found in production, a hotfix branch allows a fast, isolated patch that can be merged back into both the main line and the release branch to ensure the fix is included in future releases. This structure gives you control over what goes into each release and when, rather than tying release timing to other concerns like formatting or language choices.