← Back to team overview

launchpad-dev team mailing list archive

Yellow retrospective meeting notes: August 10


Project report


(no "tricks" section this week)

Project report Summary:
 * A vacation kept one weekly report from being written, and another weekly meeting from happening. Welcome back!
 * We're still hiring for openings in a very cool Python & cloud position, so please apply soon if you are interested! We are progressing pretty far along the process, though we have many more interviews to make. Interviews consumed gary_poster completely, and affected all of us to one degree or another.
 * Interviews have kept gary_poster from running parallel tests, but we expect that our three old bug friends are still waiting for us.
 * benji landed some diagnostic information that might help us figure out 974617/1011847.
 * bac and frankban provided IS with detailed, tested instructions for our proposed approach for IS to deploy the LXC test setup.
 * IS has approved our proposed approach to deploying the LXC Launchpad test set up. We think. We are waiting on this to be deployed.
 * The lpsetup developer story was planned (largely thanks to frankban) and implemented.
 * bac configured the integration tests for lpsetup to run with the unit tests prior to every commit to the main branch. We are using Juju to drive lxc-within-lxc on a Canonistack Tarmac instance. We think this is extremely cool for many reasons--not least of which are the presence of the working, gatekeeper integration tests.
 * We've been given a hard date to switch to our next project: September 3. Hopefully the buildbot slaves will be deployed and debugged sufficiently by then. It's a shame we didn't get to the parallel-ec2test-via-juju plan we proposed for another stretch goal, but maybe someone else will get it approved and started.

Topics summary:
 * gary_poster: reconciling staff unavailability with kanban work-in-progress (WIP) limits
 * gary_poster: OO versus functions, inversion of control, and how much agreement is important
 * gary_poster: More incremental success with our integration tests