17:00 <jsalisbury> #startmeeting
17:00 <meetingology> Meeting started Tue Sep 10 17:00:16 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00 <meetingology> 
17:00 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
17:00 <jsalisbury> ##
17:00 <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
17:00 <jsalisbury> ##
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
17:00 <jsalisbury> # Meeting Etiquette
17:00 <jsalisbury> #
17:00 <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
17:00 <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
17:00 <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
17:00 <ppisati> o/
17:00 <rtg> o/
17:00 <sconklin> o/
17:00 <bjf> o/
17:00 <henrix> o/
17:00 <smb> o/
17:00 <cking> \o
17:01 <jsalisbury> [TOPIC] ARM Status (ppisati)
17:01 <ppisati> Fixes for Calxeda's NIC and Omap4 mmc landed in S/master-next, and patches
17:01 <ppisati> to handle the DTB concatenation and the generic-lpae kernel flavour were
17:01 <ppisati> submitted to the flash-kernel mantainer.
17:01 <ppisati> In the mean time, while testing the Calxeda kernel a new panic crop up and
17:01 <ppisati> investigation is ongoingi (no LP bug was filled yet since we are still ruling out
17:01 <ppisati> the hardware).
17:01 <ppisati> ..
17:01 <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
17:02 <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
17:02 <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
17:02 <jsalisbury> ..
17:02 <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
17:02 <jsalisbury> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
17:02 <jsalisbury> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
17:02 <jsalisbury> || apw       || foundations-1305-arm64-bringup     || 2 work items ||
17:02 <jsalisbury> || bjf       || foundations-1308-kernel            || 1 work item  ||
17:02 <jsalisbury> || cking     || foundations-1308-power-measurement || 1 work item  ||
17:02 <jsalisbury> || ogasawara || foundations-1308-kernel            || 1 work item  ||
17:02 <jsalisbury> || ppisati   || foundations-1305-kernel            || 1 work item  ||
17:02 <jsalisbury> || smb       || servercloud-s-virtstack            || 1 work item  ||
17:02 <jsalisbury> ||           || servercloud-s-openstack-hypervisor || 1 work item  ||
17:02 <jsalisbury> Note: Some of the WI's listed in the table above don't show up in any of
17:02 <jsalisbury> the tracking pages due to the BP's needing to get properly assigned to a
17:02 <jsalisbury> series (ie Saucy).  I'll try to get this sorted with the BP owners.
17:02 <jsalisbury> ..
17:03 <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
17:03 <jsalisbury> As noted last week, v3.11 final has been released and we have already
17:03 <jsalisbury> rebased.  We have uploaded this to the Saucy archive and it should be
17:03 <jsalisbury> available for testing.  Please let us know your results.  We will
17:03 <jsalisbury> continue to track the upstream stable v3.11.x releases as we move
17:03 <jsalisbury> forward.
17:03 <jsalisbury> -----
17:03 <jsalisbury> Important upcoming dates:
17:03 <jsalisbury> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
17:03 <jsalisbury> Thurs Sep 19 - Final Beta Freeze (~1 week away)
17:03 <jsalisbury> Thurs Sep 26 - Final Beta (~2 weeks away)
17:03 <jsalisbury> Thurs Oct 03 - Kernel Freeze (~3 weeks away)
17:03 <jsalisbury> ..
17:03 <jsalisbury> [TOPIC] Status: CVE's
17:03 <jsalisbury> == 2013-09-10 ==
17:03 <jsalisbury> The current CVE status can be reviewed at the following link:
17:03 <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
17:03 <jsalisbury> ..
17:04 <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
17:04 <bjf> Status for the main kernels, until today (Sept. 10):
17:04 <bjf> *   Lucid - Skipping this cycle
17:04 <bjf> * Precise - Prep'ing Packages
17:04 <bjf> * Quantal - Prep'ing Packages
17:04 <bjf> * Raring  - Prep'ing Packages
17:04 <bjf> Current opened tracking bugs details:
17:04 <bjf> * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
17:04 <bjf> For SRUs, SRU report is a good source of information:
17:04 <bjf> * http://people.canonical.com/~kernel/reports/sru-report.html
17:04 <bjf> ..
17:04 <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
17:04 <jsalisbury> Thanks everyone
17:04 <jsalisbury> #endmeeting