Lean from the Trenches

Team Branches

Each team has a team branch that they use to check in and share code during development (some teams have several different types of team branches). Team branches have more lenient policies than the trunk. The code has to compile, and all unit tests have to pass, but the feature doesn’t have to be finished or tested. The team branch is there to provide a place for developers to check in unfinished code.

So, how do we keep the trunk and the team branches and all individual workstations in sync? Here’s a summary of how change flows through the system:

Basically, change flows “downward” (from the trunk to the team branches to the workstations) ...