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

[Liu, Song]

New Action Item List:
  * Song to update wiki page and the Google calendar for w4 schedules. 
  * Song to schedule the go/no-go meeting for M3.
  * Richard to follow up with Mark on bug 1325 to decide if we need this for M3 once we have the resolutions. 
  * Song to follow up with ScottR offline on doc issues: auto-generation, revisions, central location for docs changes, etc.
  
Attendees:
Beth, Tom, ScottR, Richard, Josh, Jessica, Dave, Mark, Darren, Jeff, Bruce, Song

Notes:
 
1. Opens collection - 5 min (Song)
2. M3 release criteria review - 15 min (team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
   * two high bugs remaining: 1313 already has patches, will be in for M3. 1325: Richard will follow up with Mark once we have the resolution to decide if we need this for M3.
3. M4 plan & schedule - 15 min (Beth/Song)
   * M4 focus is bug fixing. Med bugs have until the first RC build to go into Yocto 1.1. Only high/critical bugs go into 1.1 after M4 RC1.
   * First RC build is 9/6/2011.
   * Doc freeze day is 9/29/2011.
   * Final release is 10/5/2011.
4. Opens - 10 min
   * real time updates (Darren): 
     - there are real time updates coming. Hoping to have real time patches out today. We have most of them, ran into some build issues. 
     - Moving meta-rt into OE-core. There won't be meta-rt any more. 
     - For BSPs: easy for rt only. A little tricky for BSPs with both rt and no-rt.
5. Action item Review - 5 min
 
* The team to review ALL bugs they own and do some estimation. Please put the estimation on the white board by next Thursday (8/4/11): please send estimate to Song if you have not done so.
* ScottR will follow up with Paul on doc auto-generation and revision inclusion in the doc. The goal is to have docs refer to the release?: Song will talk with Scott offline.
* Song will follow up with Tracey to make sure marketing planning happens between milestones so that there is no disruption to the development schedule.: Tracey is finding an inter for the demo. No impact to the engineering team so far.