It’s about multi-team configuration management (or continuous integration). It’s fromThe BuildMaster.

• Create the mainline (public) and virtual build labs (private) codelines.
• Make sure the mainline is pristine and always buildable and consumable. Create shippable bits ona dailybasis. Use consistent, reliable builds.
• Build private branches in parallel with the main build at a frequency set by theCBT.
• Use consistent reverse and forward integration criteria across teams.
• Be aware that dev check-ins are normally made only into a private branch or tree, not themainline.
• Know that check-ins into a private branch are only reverse integrated (RId) into main whenstringent,division-wide criteria are met.
• Use atomic check-ins (RI) from private into main. Atomic means all or nothing. You can back outchanges ifneeded.
• Make project teams accountable for their check-ins, and empower them to control their buildprocess withhelp from theCBT.
• Configure the public/private source so that multisite or parallel development works.
• Optimize the source tree or branch structure so that you haveONLY ONEbranch per component of your product.