2011 12 9 workflow

who: Jonathan, Orran, Dan, Ian, Nur

We had a discussion on:

• The Github Wiki
• Git workflow
• Style issues
• Unit testing
• Some code review

The Github Wiki

We walked over the wiki and some of the articles that were on it. Integration between issue tracking and wiki was demonstrated by Dan.

Git Workflow

We want to have a linear history, Ian disagreed on doing a rebase because it breaks the history. Decided linear history is desirable, Ian will look into a mechanism to achieve this.

Style Issues

Debated whether small functions should be all on one line; decided that it is preferable for within header files.

Qualifier and return type on the first line, function name and arguments on the 2nd line.

Unit tests

• We write the unit tests in C++
• Orran didn't like test being in a seperate directory
• We need to figure out if there is a way to run individual tests
• Every test suite has a setup and a tear-down
• Our stuff are EBBs, and what we want to test is an EBB; it'll rely on a bunch of stuff. In these tests we'll bring up the core infrastructure, and we'll bring up what initialisations we need to get the tests running.
• Not just for unit testing but integration testing

Code Review

• Everything is stored in a hierarchy: l0, l1, 12...
• If you are not creating a different rep, use a different root that knows that
• Root should be specialised based on the topology of what's being shared
• Can someone get uboot working on vmware or vbox
• Chat with Rich about his kernel
• Code review early next week.