Bernie's build system workflow proposal

For information on current-day OLPC software build systems, see Build system.

The currency of this article or section may be limited by out-of-date information. There may be relevant discussion on its talk page

The labels are build stream names, and they're intended to be used much like git repositiories: anyone can create their own as needed, and maintainers can pull/push between them.

 +-----+ +-----+ +------+ +------+
 |marco| |tomeu| |bernie| |mstone| (unstable trees)
 +-----+ +-----+ +------+ +------+
    |       |       |        |
    v       v       |        |
   +---------+      |        |
   |  sugar  |      |        | . . (pull)
   +---------+      |        |
        |           |        |
        V           V        V
   +- - - - - - - - - - - - - -+
   |          testing          |  (kim, jim, walter, alex)
   +- - - - - - - - - - - - - -+
                |
                V
   +---------------------------+
   |          stable           |
   +---------------------------+

The advantage of a system like this one is that makes the process of distinguishing high-quality build-patches from low-quality ones into a close analogue of the one used for distinguishing high-quality source-code patches from low-quality ones.