Structure Your Source Tree to Support Branching

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

Your source tree structure consists of a combination of folder structure, file structure, and branch structure. Within your main branch, the following folder and file structure has been proven to work for teams of various sizes:
  • Main - container for all assets you need in order to ship the product
    • Source - container for everything you need to build
      • Code - container for source code
      • Shared Code – container for source code that is shared from other projects
      • Unit Tests - container for unit tests
      • Lib - container for binary dependencies
    • Docs - container for documentation that will ship with the product
    • Installer - container for installer source code and binaries
    • Tests - container for test team test cases

Any branches that you create off of Main will copy this folder and file structure into the new branch; for example:
  • Development – Development branch
    • Source - container for everything you need to build
      • Code - container for source code
      • Shared Code – container for source code that is shared from other projects
      • Unit Tests - container for unit tests
      • Lib - container for binary dependencies
  • Main – Integration branch
    • Source - container for everything you need to build
      • Code - container for source code
      • Shared Code – container for source code that is shared from other projects
      • Unit Tests - container for unit tests
      • Lib - container for binary dependencies
    • Docs - container for documentation that will ship with the product
    • Installer - container for installer source code and binaries
    • Tests - container for test team test cases

Additional Resources

Last edited Jul 26, 2007 at 11:40 AM by prashantbansode, version 4

Comments

No comments yet.