Yellow Squad Weekly Topics: August 10

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

Yellow Squad Weekly Project Report: August 10

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.

Yellow Squad Weekly Tricks: July 20

Summary:

• bac: Don't use seteuid with bzr
• frankban: Using deb package recipes with Distribute-based Python packages
• frankban: os.path.expanduser uses $HOME to expand '~'
• frankban: In tests, use a temporary home plus a bzr whoami before bzr commit

Yellow Squad Weekly Project Report: July 20

Summary:

• This was gmb's last week with us. Farewell from Yellow squad, and best wishes for leading Green squad!
• We're still hiring for five openings in a very cool Python & cloud position, so please apply soon! The interview process largely consumed 3/5 of the squad; next week it will affect 3/4 of us. We've had some good interviewees, and we hope to have more.
• We did not have as many test runs this week because of the interviews. Our successful test run from last week stopped this week after 42 consecutive passing runs, after which we had instances of 974617/1011847 and 1014916.
• The parallel testing machines in the data center are reportedly ready for configuration and we are now waiting for IS to get to the task.
• We tested a new package of the lpsetup code, fixed some problems, and have a working package for both the developer use case and the testing use case. The next step is to design the interactive story.
• The lpsetup code has a second integration test, this time for the LXC approach.

Yellow Squad Weekly Topics: July 13

Summary:

• benji: Juju-based integration tests are a success for incremental value
• bac/gary_poster: Is it ever OK to knowingly check in broken code?
• gary_poster: Not meeting our weekly goals

Yellow Squad Weekly Tricks: July 13

Summary:

• benji/gary_poster: Different ways to keep Juju from forcing you to repeatedly accept SSH keys

Yellow Squad Weekly Project Report: July 13

Summary:

• Parallel tests are running very well this week, with 37 successful runs in a row so far...even though we haven't changed anything.
• The parallel testing machines in the data center will reportedly be ready for us next week.
• The lpsetup code's refactoring is again at a usable milestone, and we are ready to test a new package of the code.
• The lpsetup code has its first integration test, thanks to Juju.
• In the upcoming week we intend to add more integration tests and more developer-friendly features for lpsetup.
• gmb will be leaving us to start his own squad on our team!  In related news, we're hiring.