[yocto] Minutes: Yocto Technical Team (Tuesday, July 12, 2011 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada))

[Liu, Song]

Attendees:
 
Dave, Paul, Darren, Jeff, Dirk, Richard, Josh, Tom, Koen, Saul, Mark, Denys, Jason, Beth, Song
 
Action item list:
  * Team: please take a look at the proposed post 1.1 items (yellow in the M3 table, this is a draft, may change) on the wiki page and let Song know if there is any comment or concerns.
  * Saul: talk to Jianjun, QA should work with developers to make sure we can cover more distro testing (informal) before major release. Joshua and Darren volunteers for some of these testing.
  * Song: check status with Jianjun on Stabilization tasks he owned.
  * Darren/Song: define specific deliverables of 'Fast boot time' for M3 and Yocto 1.1.
  * Saul: circulate the idea of having a Sprint B for M3 via emails.
  * Saul: check update commits (one release criteria)
 
Minutes:
 
* opens - 5 min 
  - Darren: documentation process for release, making sure we can update the README.hardware after release if needed. (no time for this one this time, will put this on next week's agenda)
 
* Review Yocto 1.1 M2 schedule (Sprint and Stabilize tasks) and Release Criteria - 15 min (Song) See details at: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
  - All M2 items are already done.
  - One M2 stabilization item is done, 3 in progress
  - QA does not have resource for N+1 distro testing for every milestone release. But will do that for 1.1 release.
  - Kernel version lock: Linux 3.0 should be released by next week. Yocto 1.1 target is 3.0+, lock in Linux 3.0 now (minimum). Will decide on 3.1 on Aug 15, the beginning of M4.
  - All M2 high bugs now are committed to make M2.
  - There are new bugs from the most recent QA test. Saul will follow up with the team.
 
* Review M3 feature list, M3 Sprint B? -20 min (Song)
  - Sync qemugl with MeeGo - Implementation: was on the drop list, Edwin feels that he may be able to work on this if BSP work progresses well. We should be clear that BSP development work takes higher priority, if this one does not make 1.1, it is fine. Will keep this one on drop list.
  - 'BSP update/intro': it should be fine without this for Yocto 1.1. Will work on this post 1.1.
  - Fast boot time: it goes hand in hand with image side reduction. Darren will define the specifics for M3/1.1 deliverables.

* Discussion of using Weighted Defect density as one of the release criteria
  - No time at this meeting for this one, will put it on next week's agenda.

* Action Item Review - 5 min (Song)
  1. Song: update Google calendar with the new bridge info (done)
  2. Darren: open a new bug to track a BBXM related issue (done)
  3. Bruce: Split bug 414 into multiple ones to work and track separately (done, bug 1204, also added feature "replace qemuppc' for post 1.1)
  4. Song: send Dexuan note about bug 1099.(done, 1099 is fixed)