[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, April 09, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

[Liu, Song]

Attendees:
Saurav, Beth, Ramana, DaveST, TomZ, RichardP, MichaelH, BruceA, KevinS, JeffP, BjörnS, Fahad, Cristian, Corneliu, JessicaZ, Ross, ScottR, Saul, MarkH, PaulE, AlexD, Nitin, Denys, Song
 
Agenda:
 
* Opens collection - 5 min (Song)
* 1.3.1 release update:
  - Beth: We hit some AB issues creating the build last time. These are the same issues facing 1.4. should have been fixed last night. Started another last night. At this point it looks ok. Needs to check on some files, the world build etc. before release. 
 
* Yocto Project 1.4 M5 release readiness review - 10 min (CCB/community)
 
  - Status: We had a full pass run on RC2, RC2 had a blocking issue. It's been resolved and verified in RC3. Now RC3 is still under full pass run. 
  - Would like to have a decision on: 
    1. Shall we release M5 considering we are close to the final 1.4 release. It's no harm as far as our release team can still handle it (Beth: not much work, probably a couple of hours). It probably will not make much real different since it's already served its purpose as a checkpoint for the project and for the team. But we don't want to skip M5 and let others think that there is something seriously wrong.
      . Decision: Make M5 release. 
    2. If we still release M5, after the full pass report comes out, can we release it without another review and CCB meeting? a light release of M5? Will we announce the release?
      . Decision: It's a CCB decision. Will have the review meeting after QA report is out.
 
* Yocto 1.4 status - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status
  - It's all about bugs. As of last Sunday, we have 314 standing open. There are various reasons for people to open more bugs at this time. As I have mentioned at the beginning of the milestone, we really need to keep focusing on bug fixing in this stabilization milestone. The cutoff day is coming this weekend. So basically we cannot stressed more how much we should focus on bug fixing.
  - RP: Qemu issues update, random sanity failures, it's interesting bug, happened on multiple qemu archs. Double fault, have done lots of investigation. Applied one patch from qume master to qemu 1.4. Things seem to stabilize now.
 
* SWAT team rotation: Bogdan Marinescu -> Saul (would like to keep an eye on the build). RP/Song: Thank Bogdan for sorting through lots of AB issues in the past week. 
 
* Opens - 10 min 
  Ramana: Proposed Post build configuration as a 1.5 feature (https://bugzilla.yoctoproject.org/show_bug.cgi?id=4106). Would like comments and feedback. The YP team is concentrating on bug fixing, stabilizing 1.4 for release now. Will provide feedback once 1.4 is out.
 
* Team Sharing - 20 min
  - AlexD: looking through various bugs sending various patches to stabilize the release until Sunday. 
  - Cristian: worked on issues related to build appliance. Fixed almost all the issues. Working on connman issues, work in progress. Still one medium+ bug. Routerstation bug, have a fix for it. should be fixed this week, 4203 is high, working on it.
  - MichaelH: replacing memory for AB 6, caused some problems, fixed. A strange issue on some memory errors, able to fix it. Passed memory test, AB is back in service. Ordering extra hardware (2 additional AB this year). autobuild.yoctoproject.org/intel gateway issue should be fixed. Working on package later index.
  - Beth: quick update on AB performance. 6-7 hours on old AB. 5 hours 43 minutes on new one, 45 minutes less. With AB6 on line, it will be 4 and half hour. 15-20 more minutes less. Altogether, can reduce about an hour off build time. Michael: Build faster and more often is good. The storage is building up fast at the same time. Looking at ways to clean up. Monitoring the space usage. RP: there might some optimization on what images we are building, etc. Can someone file an enhancement bug ? (Michael will do that).