Release Review: 2012.09

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

Past reports

Key Points for wider discussion

Release Highlights

Blueprint Bump List

Android

Highlights

  • Good work and lots done.
  • Hotspot analysis for ARM sorted out
  • android toolchain continues to perform well
  • Thursday platform planning meeting before release worked really well.
    • Thursday Android planning meeting on release week came out of this
    • Maintain priorities of planning items

Issues

  • Weekly sync with landing team is not working.
    • Agenda is not being updated
    • actions not being followed up on
  • similar issue with the working groups
    • ACTION: follow up with process issues
  • Need more infrastructure support for the things that the Android team requires.

Lessons Learned

  • Infrastructure Roadmap has to be publicized and communicated to the organization
  • Going forward, post mortem will be the last team meeting of the cycle and the team meeting will be in hangouts.

Developer Platform

Highlights

  • Good progress on ARMv8 bootstrapping. OpenEmbedded image booting.

  • Linux Linaro worked well this cycle. We’ve got ST-E team on board.
  • Linux Linaro Core tree is up for a more stable kernel (as request by Landing Teams). Intended to merge stable updates.
  • UEFI support is here!
  • Better understanding of ARMv8/OpenEmbedded/FastModels.
  • Have aarch64 cross-building quantal chroot working
  • Multi-arch Perl/Python exists and seems to work (still things to test).
  • Linaro U-Boot released late.

Issues

  • Problem with LAVA. The dashboard wasn’t available.
  • Privacy on ARMv8 was confusing. This topic should be mandatory for each projects and clarified early.
  • Privacy isn’t well handed. Especially, communication. Very hard to know what is/isn’t OK to send out.
  • Privacy is a bad thing full stop in organisation working on free software.
  • Jenkins related problems (best practices, helpers needed). When you maintain a lot of job

Lessons Learned

  • Discuss project privacy (public/private).
  • Need better procedures to work with Linux Linaro trees.
  • Documentation is very important. Someone is always going to ask it at some point.
  • Lack of guideline to handle private projects (communication, repositories, blueprints).
  • Use upstream - sometimes they just do your work for you (perl multiarching)

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

  • Process implemented for LAVA work requests from stakeholders.
  • New hire performed extremely well
  • some work done under the radar should pay off in coming months
    • image filters for LAVA
    • cleanup of documentation

Issues

  • Wiki pages for process is very obsolete
    • need to update

Lessons Learned

  • Planning process - meeting with asac, dzin, doanac for Thursday.

Infrastructure

Highlights

  • Plenty of bugs to solve
  • Fairly average cycle
  • Daily hangouts continue to be useful
  • Effective cycle, new stuff to work on
  • smooth cycle.
  • Switch between maintenance and development keeps engagement level high
  • Good collaborative work, fosters working relationships
  • A few shorter blueprints are good. The amount of work seems to be about right.
    • coming in sooner on the planning process might be useful.
  • interesting cycle, for new interesting features development
  • good exposure to LAVA stuff
  • lots of code rollout
  • many things to work on
  • better communication with other teams
  • A good cycle in terms of deliveries - high percentage delivered.
  • one week cycle shift one week forward worked out very well
    • awkward on release week.
  • #linaro-infrastructure IRC channel is being well used and is facilitates good communication

Issues

  • Slow interaction with IS issue, but IS is quite responsive.
  • If coming onto maintenance, leaving unfinished development is not satisfying
  • secondary priority blueprints are always left to the end. * 2
  • Need ramp up time for working with other teams development
  • working with people in different time zones is a challenge.
  • planned paired programming, but it did not work as well due to time constraints
  • get more information about what is happening in other teams
  • interface with Infrastructure team remains a problem
  • confusion with the planning process
    • in progress, solution is being developed at a high level

Lessons Learned

  • Key is to do the work without IS involvement.
  • Jumped into code too early, should have planned execution better
  • pester people on IRC to expedite delivery of dependencies.
    • everyone is encouraged to help people
  • Off hour working is sometimes the only way to communicate effectively
  • as Linaro grows, processes will change; it is important to communicate things that do not work the way they used to.
  • Maintenance team is extremely useful for keeping ongoing development current and correct.
  • predicting issues and raising them as soon as they come up is a good thing.

Samsung Landing Team

Highlights

Issues

Lessons Learned

QA

Release

The release week standup meeting for platform has certainly be useful for the QA team because Paul has usually interacted with the Release team and has been the bridge between the teams. We explained how is the workflow is during the release week and clarified the process for newcomers.

However, for the release team, it hasn't been helpful. There is still an effort to manage the same quantity of mails across teams, coordination effort has been the same, tracking deliveries is also the same.

There is probably too much spreadsheets/documents to maintain. It's starting to be a mess to find which document is really used to track. There's also a lot of duplication in the spreadsheets. In addition, there should be a single document to track the release builds, but a pad and a google doc spreadsheet could be sufficient.

Lessons Learned

The tools to keep everybody on the same page are real time sync up (IRC), notifications/status update e-mails, spreadsheet for Android/pad for Dev Platform. Everything is happening during the release week, not much before. The workflow/plan doesn't change.

Cycles/1209/Release/Review (last modified 2012-10-11 18:06:47)