Minutes: Yocto Project Technical Team Meeting - Tuesday, October 09, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

["Liu, Song" <song.liu@intel.com>]

Sorry for the late. 

Attendees:
ScottR, Jessica, Beth, DaveST, PaulE, Richard, Sea, Fahad, DavidW,  Denys, AlexG, Ross, Song
 
Amit: MontaVista, based in India, Bangalore. Replacing Mark in this meeting for MontaVista
Dave, Michael, 
 
Minutes:
 
* Opens collection - 5 min (Song)
* Yocto 1.3 status  - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status  
  - RC4 is due out tomorrow. Larger, invasive less possibility going in. 3.4.10 kernel caused segfault on arm. We are going to move to 3.4.11. Master is still in bug fixing mode. At the moment we will take everything into the release branch. Hoping to release RC4.
  - If you expect anything in the release, please get them in today. If you.
 - Medium+ bugs review: https://bugzilla.yoctoproject.org/buglist.cgi?bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&list_id=16013&priority=Medium%2B&query_format=advanced&target_milestone=1.3&target_milestone=1.3%20M1&target_milestone=1.3%20M2&target_milestone=1.3%20M3&target_milestone=1.3%20M4&target_milestone=1.3%20M5&target_milestone=1.3.1&target_milestone=1.3.2&order=assigned_to%20DESC%2Cpriority%2Cbug_status%20DESC%2Cbug_id&query_based_on=
 
3176: delay to 1.4. not doable, easy to workaround, release note this one.
1640: How to document, it will be wiki for 1.3 release
3080, release note.
3231, release note.
  - Non-bug issues: Paul to send song email.
 
* SWAT team rotation: Saul
* Opens - 10 min
* Team sharing - 20 min
  - Paul: documentation and bug fixes recently. Got some time to release the build history tool. This is a little web app allows you to go through warning, mark each one needing attention. Will send email today with more details. Publish the meta-webserver layer. Apache, modphp, php myadmin. It's functional, but there are some bugs. Still working on it. RP: QA can use this. 
  - Michael: last week SSD upgrade on servers. worked with Beth on release prep. Working on some of the internal servers, space issues, etc.
  - Beth: Last week worked with Michael on external ABs. should speed up build time a little bit. Working on 2 release script. 1.main YP release script. It does major release. Related to the eclipse bug. Single push button. 2. release script for people using YP to build and release with GPL compliance. Bring together all the source code, release, etc. together. 
  - David Wolf: if you submit a patch, how do we know if it is applied. Saul: we review the patches on the mailing list. Saul pull into Master under test, then send to Richard. Richard pull them into master. There are times Richard see something to be directly pulled in without MUT. You should see a email if it's merged. If you don't see any response, ping it. 
    . RP: for managing the balance of updating to the latest master and maintaining a queue of un-merged patches, recommend looking at Git, probably maintaining a branch in git with master update/rebase and local fixes. If the master does merge those patches, rebase. 
    . Some fixes on master will be back ported to stable releases. The patches need to be based on master generally, then back ported. Read only http pull (Michael has been working on) will help.