Release Review: 2012.06

  • Created: David Zinman <david.zinman AT linaro DOT org> Past reports

Release Highlights

Blueprint Bump List

Android

Highlights

Good cycle, Connect was "seamless" and well attended.

Most items were on track.

Bero's youtube video has given Linaro a lot of publicity.

Issues

Lots of vacation time for the team during the cycle

Lessons Learned

Connect doesn't necessarily have to interrupt things

  • - For some reason connect did not disrupt the team possibly because it was on the release week.
    • - planning was able to be done efficiently at connect since most of the Android delivery was delivered the week before.

Developer Platform

Highlights

Kernel Changes were useful, consensus on changes have been agreed to

  • - on shared config, using config fragments - Now also containing a shared ubuntu config fragment

Linux-linaro tracking went fairly well

  • - Tree published right at the beginning of the cycle

OpenEmbedded work started - there is LAMP like image (with Lighttpd instead of Apache) which works fine with Wordpress (not part of image) - there were some toolchain issues but got solved with help from Khem Raj (OE toolchain maintainer) - created http://git.linaro.org/gitweb?p=openembedded/meta-linaro.git repository (based on Ken Werner work) with some updates - created http://git.linaro.org/gitweb?p=openembedded/jenkins-setup.git repository with initial scripts for ci.linaro.org jobs - build takes ~60GB of space and 6-8h on i7-2600K xbuild functionality is progressing well:

  • - Package and instructions in a very useful way - GSOC progressing well at Debian

Kernel package scripts should be good, but not in Jenkins yet.

Issues

A bit of overplanning due to connect which ate into planning time. Cycle's that work around Connect must be better planned. Linux Linaro Tracking:

  • - Each LT uses own base - Not necessarily all the teams maintained a branch for the 3.4 kernel - Once a new version is released (e.g. 3.5), the LTs need to tag the previous version to make those available -- when LT moves their tracking tree base from one -rc to another, the most recent version using the previous base must be tagged. This must be done per -rc, doing that per kernel release is too coarse - Not that many tests over the cycle, which should be improved with the CI jobs deepti created at Jenkins

Bootstrap mechanism not agreed as correct way to integrate upstream Debian Freeze date moved to end of cycle Bug list/task tracking related with multi-arch and cross build should be separated for Ubuntu and Debian Cross builds running daily can be an issue on the current machine

  • - Might be useful to move to an external machine (cloud?)

Canonical cloud is slow.

Lessons Learned

It's up to the team to plan properly around connect - pre or post connect Keep separate Debian and Ubuntu cross- bugs/issues/tasks lists to help track what is fixed where/when.

Graphics

Highlights

Issues

Lessons Learned

Kernel

Highlights

Issues

Lessons Learned

Multimedia

Highlights

Issues

Lessons Learned

OCTO

Highlights

Issues

Lessons Learned

Power Management

Highlights

Issues

Lessons Learned

Toolchain

Highlights

Issues

Lessons Learned

LAVA

Highlights

Lots less failures, down from ~30 to 7 a week New method of deploying releases to servers. High number of blueprints delivered

Issues

Monday blueprints implementation is difficult

Lessons Learned

Infrastructure

Highlights

Maintenance team worked on a lot of bugs

  • - Released LIT - Good way to learn the infra team's projects

Hangouts are very useful for cooperative development +2 Test-driven developement is very useful Maintenance team of Deepti and Milo did a great job. +2 Mostly hit work items for tight deadlines

Issues

Some build system issues that were resolved

  • - builds getting queued because slaves were not coming up

Documentation is hard to find

  • - wiki can be improved

System management vs Software development

Lessons Learned

Maintenance team process is working out very well. Deployment issues: missing libraries on production platform (development machine != server to deploy on: servers tend to be on old, stable releases. Need to pay more attention to this during dev.) Paired programing works well.

  • - really facilitates problem solving

Keep the maintenance team rotations, working very well. Planning, planning, planning.

Samsung Landing Team

Highlights

Issues

Lessons Learned

Release

Highlights

Issues

Lessons Learned

Key Points for wider discussion

Cycles/1206/Release/Review (last modified 2012-07-03 14:08:11)