This project is read-only.

How to organize your source tree

- 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 o 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 ships with your product
    • Installer – Container for installer source code and binaries
    • Tests – Container for test team tests

Any branches that you create off of the Main branch will copy this folder and file structure into the new branch; for example:
  • Development – Development branch
    • Source – Container for everything you need in order 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 in order 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 ships with your product
    • Installer – Container for installer source code and binaries
    • Tests – Container for test team tests

Additional Resources

Last edited Jul 31, 2007 at 4:12 PM by prashantbansode, version 7

Comments

No comments yet.