問題文
A team of six is starting to use a repository. Two features are being built at the same time and only one of them will go into the next release. What branching arrangement is the simplest one that meets this need?
選択肢
- A single shared branch for all work, with each developer committing directly to it and using a naming prefix on component names so that the release manager can identify which components belong to which feature at deployment time and exclude the ones that are not ready.
- One branch per developer, merged into the mainline at the end of each day.
- One branch per environment, so that each sandbox has a branch that mirrors its current state and the release manager can see at a glance what is deployed where without querying the orgs.
- One branch per feature, created from the mainline and merged back only when the feature is complete.