Postmortem and lessons learned for Linaro's release 2012.08

https://wiki.linaro.org/Cycles/1208/Release/Review

Highlights and Key Successes ============================ Linaro also held its first Virtual Connect event on 13 - 17 August, 2012. This online event used Google+ Hangouts on Air and was streamed and recorded via YouTube. Members of the various Linaro Teams provided informative, educational and exciting sessions that allowed for public viewing and participation. http://plus.google.com/u/0/b/112814496864921562564/116754366033915823792/pos...

The Android team created stable Jelly Bean builds from AOSP and an Android benchmarking platform to automate many of the tests in the AOSP codebase.

The Developer Platform Team announced USB Host enablement is now available in LAVA and that all packaged linux-linaro kernels are now cross-compiled and boot tested via LAVA before they are uploaded to Linaro Overlay PPA. Additionally, U-Boot-Linaro is now based on the latest upstream release--v2012.07.

Postmortem and Lessons Learned ==============================

This cycle was fairly low key: lots of people were out for vacations and many others were attending external conferences such as Linux Plumbers.

One issue of concern was the deployment of an infrastructure project on the last week before release. A the new django application was deployed on snapshots.linaro.org that disrupted several builds on the Friday before the release. The issues took one week to resolve. The issues are: - The deployment was not communicated and broadcast properly - Build maintainers were not given proper warning - deploying new functional software on a Friday with no one available on the weekend for emergency - deploying during a release week A big "thank you" is in order for Georgy Redkozubov (gesha) for his help and availability in troubleshooting and getting it fixed.

An incident report has been filed here: https://wiki.linaro.org/Internal/Process/DealingWithCrisis/IncidentReports/2...

Blueprints ========= The number of high or essential priority blueprints that missed the cycle: Android 3 out of 13 Developer Platform 0 out of 3 Infrastructure 1 out of 6 Lava 2 out of 4

Total 6 out of 26

23% of high or essential priority blueprints scheduled for this cycle were not delivered.

Total blueprints: 14 out of 49 missed the cycle.

High priority missed blueprints recap: 12.05: 19 out of 48, 39% 12.06: 13 out of 31, 42% 12.07: 14 out of 31, 45% 12.08: 6 out of 26, 23%

* Not included is data from working groups and landing teams

Source: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AjEaTwrvj1bidGhNZH...