Typical branch duration: Which statement is accurate?

Typical branch duration: Which statement is accurate?

• A. It doesn't matter.
• B. Shorter is best all the time.
• C. Long-living branches are better for small teams.
• D. Shorter is best, but long-lived branches may be appropriate in some cases.

Answer: (D)

Focusing on how long branches should live in typical development workflows, the goal is to keep feedback fast and risk low. Short-lived branches tend to be merged quickly, which reduces drift, surfaces integration issues early, and aligns well with continuous integration and code review cycles. This is especially valuable for small teams, where waiting on long-lived branches can bottleneck progress and make merges more painful. There are valid real-world scenarios where longer-lived branches are appropriate: large features that span many components, coordination across multiple teams, or release stabilization and regulatory or QA processes that require extended work without constant merging. In those cases, a longer-lived branch can prevent excessive context-switching and allow focused work, provided there’s a plan to integrate and release it eventually. So, the best statement is that shorter is best, but long-lived branches may be appropriate in some cases.

Focusing on how long branches should live in typical development workflows, the goal is to keep feedback fast and risk low. Short-lived branches tend to be merged quickly, which reduces drift, surfaces integration issues early, and aligns well with continuous integration and code review cycles. This is especially valuable for small teams, where waiting on long-lived branches can bottleneck progress and make merges more painful.

There are valid real-world scenarios where longer-lived branches are appropriate: large features that span many components, coordination across multiple teams, or release stabilization and regulatory or QA processes that require extended work without constant merging. In those cases, a longer-lived branch can prevent excessive context-switching and allow focused work, provided there’s a plan to integrate and release it eventually.

So, the best statement is that shorter is best, but long-lived branches may be appropriate in some cases.