Postmortem and lessons learned for Linaro's release 2012.06
https://wiki.linaro.org/Cycles/1206/Release/Review
Highlights and Key Successes ============================ Release 12.06 highlights the Android team's multimedia enablement being review on AOSP, and the update to Android version 4.0.4 r2. The video of Bero demonstrating the efficiency of the Linaro Android toolchain has now garnered over 230,000 views on Youtube.
http://armdevices.net/2012/06/02/linaro-improvements-to-android-4-0-4-perfor...
The Ubuntu team has created and published a new Linux Linaro branch, called Linux Linaro Tracking It contains the 3.4 Landing Team trees from TI, Samsung and ARM, delivering a single and unified tree which helps identifying conflicts and issues ahead of upstream.
Postmortem and Lessons Learned ==============================
Most of the topics for this cycle revolve around Linaro Connect. The success of the event is dampened by the shortened development cycle it creates. This time, Linaro Connect occurred over a release day. While this presented some challenges, some interesting positive issues were observed.
Connect doesn't necessarily have to interrupt things. Possibly because of release week, planning for the cycle was accomplished while the teams were in the same location, which made issue resolution quicker and easier to discuss. Teams should follow this example to get code in early and use release week to plan for the next cycle. So it is up to each team to plan for pre and post Linaro Connect as well as planning for the cycle.
The Infrastructure team has been experimenting with paired programming and a maintenance team. Each cycle 2 infrastructure engineers take the maintenance rotation to deal with high priority bugs and occurring issues. This is working very well and has helped facilitate speedy resolutions to some problems that came up during the cycle.
Blueprints ========= The number of high or essential priority blueprints that missed the cycle: Android 5 out of 12 Developer Platform 3 out of 10 Infrastructure 4 out of 6 Lava 1 out of 3
Total 13 out of 31
42% of high or essential priority blueprints scheduled for this cycle were not delivered.
Total blueprints: 31 out of 61 missed the cycle.
High priority missed blueprints recap: 12.05: 19 out of 48, 39% 12.06: 13 out of 31, 42%
* Not included is data from working groups and landing teams
Source: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AjEaTwrvj1bidHZPLU...