Release Review: 2012.10

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

Past reports

Key Points for wider discussion

Release Highlights

Blueprint Bump List

Android

Highlights

  • Great Connect prep, had a steady cycle
  • Things have been generally good, Even the ST-Ericsson Snowball team actually delivered something. :)

  • 4.1.1-r6 and 4.1.2 updates, native toolchain
  • overall everything went fine even though there were 2 new upstream releases (4.1.1-r6 and 4.1.2), but some minor stuff had to be moved around

Issues

  • ETA's for new boards were fuzzy
  • Some blueprints can be a bit large. Big blueprints should probably be split into smaller work packages.
  • I has been hard to get the work on tracking snowball going
    • Mainly communication problems.
  • Could have used some help with crt*.o aarch64 porting

Lessons Learned

  • Connect + releases was a lot of work at the end of the cycle
  • goals and Connect people generally seemed busy, but not overly busy
  • Should improve the BP(s) for tracking snowball to get Axel and Ushit working in the same direction together.
  • Should discuss Snowball builds with Bejram at connect to get the ST-Ericsson view on Snowball builds.

Developer Platform

Highlights

  • Something new - browser benchmarks
  • Uneventful cycle
  • aarch64 sprint was useful and went well
    • working with upstream people worked very well
  • Multi arch is finally done
  • Openembedded and armv8 is new and progressing well
  • Open embedded is nice to work with
  • No new kernel, easy cycle
  • Some progress with fixing Jenkins script and kernel configuration for booting in LAVA
  • linux-linaro added to the CI loop
    • origen boots with CI script

Issues

  • Android patch in the Snowball tree caused an issue
  • Fairly low key cycle
  • Work assignment not very clear
  • monthly release can be frantic with too much overhead
  • engineers joining and leaving the team create overhead and churn
  • blueprints within the monthly cycle don’t necessarily fit the delivery schema
  • toolchain work in OE takes a long time to recompile
  • IS can be slow in resolving issues
  • Most kernels still do not boot in LAVA
  • not clear how to handle requests for stable trees.
  • planning could have been better, a lot of unexpected work came in during the cycle

Lessons Learned

  • Take initiative on work assignments, make sure you know what you will be doing
  • don’t update oe unless you have extra time
  • emphasis on linux-linaro core tracking tree for better use by working groups and the community

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

  • Planning session was useful, but can get more accurate
  • Process integration is working well

Issues

  • Need to clean up the LAVA backlog

Lessons Learned

  • Blueprint not started should go back in the backlog
  • Acceptance criteria needs to be useful for delivery

Infrastructure

Highlights

  • Good month, more learning and experience
    • jquery, java-script, git, nice change of pace
  • lots of agility exhibited by the team
  • Good team cooperation
  • Maintenance: Busy month at the beginning. Slow down a bit
  • Challenging project, delivering at the last minute
  • Team did well with self direction

Issues

  • Jenkins: No good plugins for upstream jobs get status of downstream projects, MultiJob plugin works for us partially

    • one view for all the downstream tests for a particular job
  • Spec changes at last minute was very hard to deal with
  • not enough testing/iterations
  • Did not show work to stakeholders early enough
  • on maintenance, some periods in the cycle became boring
  • absence from Android build left a building instability
  • Setup of ARM 64 builds were not planned as well as they could have been
    • created much more work for the maintenance team
  • Multiple inputs to the project created churn
  • Some changes were snuck into projects at the last minute
    • created higher risk
  • Connect is always disruptive
  • improve how maintenance works

Lessons Learned

  • can submit plugin requests to the LAVA team
  • come up with a better pre-implementation requirement gathering strategy
  • spent too much time on implementation before a prototype was shown to stakeholders
    • better requirements gathering and rapid prototyping would help
  • Google Docs Diagraming can help
  • Creativity and working with people can help define new ways of working
  • In the future to tune tools for better usage and integration into Linaro
    • help in the daily workflow
  • for any boring period, look for something interesting to focus on
    • as team lead, and others
    • look for ways to automate these tasks
  • for burning fires determine what issues are high and create a plan to resolve them
    • take a lead
  • act as a tiebreaker for external disagreements
  • if extra effort is required, time off can be considered
  • for cycles that are affected by connect, plan the cycle around connect
    • week before connect, use half for milestone and half for connect participation
    • use items from connect in the milestone

Samsung Landing Team

Highlights

Issues

Lessons Learned

QA

Release

Lessons Learned

Cycles/1210/Release/Review (last modified 2012-10-30 14:02:49)