Release Review: 2012.07

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

Release Highlights

Blueprint Bump List

Android

Highlights

Benchmarking for ARM was pretty successful Good support from the LAVA team - having people across timezone really helps

In the face of adversity, the Android team did really well. Good team dynamics. - good participation

QA team has begun to be an excellent asset to development.

Issues

External Linaro resource did not pull their weight for Snowball development - enablement did not happen from the resource.

Lack of alignment with infrastructure team

Infra team had holidays or were not otherwise available due to timezone issues

Current Jenkins builds are unreliable ACTION: dzin to follow up on Jenkins reliability

Fire-drills create confusion and cause engineers to lose focus

dd images not sanctioned by Android team.

Cross team work is not functioning properly.

Lessons Learned

Need to determine how to accomplish enablement with minimal support from member companies. We need to drive the process

Work definition between teams should be well defined.

Developer Platform

Highlights

All images published Monday morning

  • - gave ample time to have a respin and testing

Kernel CI jobs working nicely

  • - have a bit more work to do

Linux linaro project is going very well

  • - big.LITTLE changes integrated

Finally able to deliver two major changes requested from ARM:

Teams worked very well with late requirements coming in from external sources. Infrastructure team was great to cooperate with. Helped with OE based jobs Debconf was quite useful based on the topics we invested at Linaro lately:

  • - Multiarch - Cross support
    • - Bootstrap - Breaking dependency cycles
    - Cross toolchain

Issues

Requirements came in late for external sources

  • - created confusion and scrambling

Some Jenkins issues, but it was at least up for the whole release week. LAVA testing for CI builds needs more attention

  • - some tests are board specific, some lava specific, some not configured completely - NO LAVA testing on linux-linaro yet
    • - ACTION: Andrey to sync with deepti - ACTION: Andrey to open a bug against LAVA for linux-linaro testing

Multiplatform topic created some problems for linux-linaro

  • - ACTION: Andrey to write up in summary, send email to other groups describing the problem

Release schedule is such that linux-linaro releases are at the same time as Linux releases

Lessons Learned

Need to discuss the merge cycle within development cycles. ACTION: dzin, rsalveti, asac to schedule.

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

Dave Pigott created blueprints for hardware deployment LAVA Monitors helped determine LAVA stability

Issues

Losing resources Requirements coming in mid-cycle Unpredictability of lab work.

Lessons Learned

Planning process is a good thing:

  • - blueprints created for requirements make things clear

Infrastructure

Highlights

CI Skeleton Dashboard

  • - some paired programming but limited by time differences - went well though as one picks up after the other

Image tools paired programming skillset is getting stronger

  • - hangout work well - tried Cloud 9 service (online IDE) - c9.io
    • - code editor like etherpad - worked ok, but not ideally. Needs more development, not ready yet.

Good cycle

  • - django experience gained, good effort for ramping up. - good knowledge transfer

Issues

Jenkins library had problems when it was implemented

  • - had to back it out and use another library

Still no staging service, ticket 518

  • - relying fully on IS services for deployment

Lots to learn, can overwhelme development time.

Lessons Learned

From Jenkins issue: use small examples to test the libraries and determine stability. Good to have services written in same language

  • - easier to maintain, code portability and reusability

"Never underestimate your blueprint"

  • - blueprints can be detailed, it is good to discuss any items that are not clear - consult the blueprint on a regular basis.

Knowledge transfer is very useful at the end of the cycle

Paired programming and hangouts benefit from pre-organization and a published agenda. - one of the pair researches while the other codes A third person do a code review is useful

Samsung Landing Team

Highlights

Issues

Lessons Learned

Release

Highlights

Issues

Lessons Learned

Key Points for wider discussion

Cycles/1207/Release/Review (last modified 2012-08-01 14:45:50)