Which set of branching strategies is commonly used for team collaboration in software projects?

• A. Feature branches, release branches, and trunk-based development.
• B. Single trunk with no branches.
• C. Random branch per commit.
• D. Branching is not used in modern workflows.

Answer: (A)

Collaborative software work relies on structuring work so multiple people can build, test, and release without stepping on each other’s changes.

Feature branches let developers or small teams work on a new feature or fix in isolation, then merge back after review and testing. Release branches provide a dedicated path to stabilize and finalize a release—bug fixes and polish can happen there while ongoing work continues on the main line. Trunk-based development centers on a single main branch that everyone integrates into frequently, keeping the codebase in a deployable state and surfacing integration issues early.

Together, these approaches balance isolation with regular, integrated progress, which is why this set is commonly used for team collaboration. The other options would either force too much change on the main line, create chaotic branching, or ignore established modern workflows.