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

[Liu, Song]

Really sorry if many of the past meeting agenda and minutes have not been able to reach you. I had some problems with the Yocto project mailing list. Please let me know if you hear anyone still having this problem.

Thanks!
Song

Attendees:
Mark, Dave, Paul, Shane, Saul, Beth, Richard, Josh, Jason (TI), Darren, Sean (Dell), Song
 
New action list:
 
  * Team: please take a look at the post 1.1 items 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.
  * Beth/Darren/ScottR: document the central location in the release, and put any doc changes in the location after release.
  * Song to setup go/no-go meeting next Monday to decide on the M2 release.
 
Agenda:
 
- opens - 5 min 
- Review Yocto 1.1 M2 Release Criteria - 20 min (Song) See details at: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
  * All M2 features are completed.
  * 'Lock kernel version' should be moved to M4 and will be completed between 8/8/11 and 8/15/11.
  * All release criteria are green except testing related ones. Please see the wiki page.
  * For M2 release, we should let Beth go ahead with the release as if we would be releasing M2 on time next Monday. On the other hand, we let QA run the full test. We will have a go/no-go meeting next Monday to decide if we release M2 based on the full test result of RC3.
 
- Review M3 status and schedule - 10 min (Song)
  * All M3 committed features are on track. We need someone to handle multi-lib 9 and 8 tasks after Mark is done with them.
  * Darren's two features (reduce image size and reduce boot time) should be all marked risky for M3. Darren will work on them separately in independent layers that won't affect 1.1 release so that his development work can be extended with more time.
 
- Discussion of using Weighted Defect density as one of the release criteria: (4th graph at: https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend ) - 10 min
 
  * The team has concern that this will discourage developers from filing bugs.
  * There is no perfect measure but it's better if we have measure to make sure we deliver quality software.
  * This should not discourage QA and developers in the community from filing bugs.
  * There are a lot of fixes that went in without leaving a track in Bugzilla.
  * We will talk about this in 1.2 planning and try this out in 1.2 development and see how it goes.
 
-  Opens - 10 min
  1. Darren: documentation process for release, making sure we can update the README.hardware after release if needed.
    * We should have a central location for putting doc changes after release. We don't have to update the release tarball.
 
 
- Action Item Review - 5 min (Song)
 
Action item list:
  * 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. (Done)
  * Darren/Song: define deliverables of 'Fast boot time' for M3 and Yocto 1.1. (Done)
  * Saul: circulate the idea of having a Sprint B for M3 via emails. (Done). Will just extend Sprint A to 27th.
  * Saul: check update commits (one release criteria) (Done)
  * Team: please take a look at the post 1.1 items on the wiki page and let Song know if there is any comment or concerns.