17:00 <jsalisbury> #startmeeting
17:00 <meetingology> Meeting started Tue Mar 24 17:00:14 2015 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00 <meetingology> 
17:00 <meetingology> Available commands: action commands idea info link nick
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/Vivid
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 <cking> o/
17:00 <henrix> o/
17:00 <apw> o/
17:00 <kamal> o/
17:00 <bjf> o/
17:00 <ppisati> o/
17:00 <smb> o/
17:00 <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
17:00 <sforshee> o/
17:01 <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
17:01 <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
17:01 <jsalisbury> ..
17:01 <jsalisbury> [TOPIC] Status: Vivid Development Kernel (ogasawara)
17:01 <ogasawara> Our Vivid kernel has been rebased to v3.19.2 and uploaded, ie
17:01 <ogasawara> 3.19.0-10.10.  We are approaching kernel freeze for Vivid.  It is
17:01 <ogasawara> ~2 weeks away on Thurs Apr 9.  If you have any patches which need to
17:01 <ogasawara> land for 15.04's release, please make sure to submit those asap.
17:01 <ogasawara> -----
17:01 <ogasawara> Important upcoming dates:
17:01 <ogasawara> [LINK] https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
17:01 <ogasawara> Thurs Mar 26 - Final Beta (~2 days away)
17:01 <ogasawara> Thurs Apr 09 - Kernel Freeze (~2 weeks away)
17:01 <ogasawara> Thurs Apr 23 - 15.04 Release (~4 weeks away)
17:01 <ogasawara> ..
17:01 <jsalisbury> [TOPIC] Status: CVE's
17:02 <jsalisbury> The current CVE status can be reviewed at the following link:
17:02 <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
17:02 <jsalisbury> ..
17:02 <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)
17:02 <bjf> Status for the main kernels, until today:
17:02 <bjf> *   Lucid - None (no update)
17:02 <bjf> * Precise - Prep
17:02 <bjf> *  Trusty - Prep
17:02 <bjf> *  Utopic - Prep
17:02 <bjf> 
17:02 <bjf> Current opened tracking bugs details:
17:02 <bjf> * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
17:02 <bjf> For SRUs, SRU report is a good source of information:
17:02 <bjf> * http://kernel.ubuntu.com/sru/sru-report.html
17:02 <bjf> 
17:02 <bjf> 
17:02 <bjf> Schedule:
17:02 <bjf> 
17:02 <bjf> Current cycle: 20-Mar through 11-Apr
17:02 <bjf> ====================================================================
17:02 <bjf> 20-Mar   Last day for kernel commits for this cycle
17:02 <bjf> 22-Mar - 28-Mar   Kernel prep week.
17:02 <bjf> 29-Mar - 11-Apr   Bug verification; Regression testing; Release
17:02 <bjf> ..
17:02 <jsalisbury> [TOPIC] Review of sforshee upload rights
17:02 <apw> sforshee, hi
17:03 <sforshee> apw: hello
17:03 <apw> could you introduce yourself, perhaps tell us a little about yourself
17:03 <kamal> *cough*
17:03 <apw> (for the record)
17:03 <sforshee> I've been a member of the kernel team for 4 years now
17:04 <sforshee> working on various and sundry things, including some packaging of kernels and related packages
17:04 <sforshee> https://wiki.ubuntu.com/SethForshee/PerPackageUploaderApplication
17:04 <sforshee> I'm looking to get PPU rights to the linux-* packages to ease the work I've been doing
17:05 <apw> i believe we have most of your sponsors here today, so if anyone wants to comment now is the time
17:06 <apw> otherwise i think the majority of the approvers have works with you over the last few months
17:07 <kamal> I stand by my sponsorship statment:  Seth is diligent and careful:  all good for linux-* ppu upload rights :-)
17:07 <kamal> ..
17:07 <ogasawara> I have not specifically sponsored a package of seth's but I've seen the work he's been doing (turning the crank on stable trees, handling linux-firmware, etc.).  He's being doing a great job..consistent, methodical, careful.  I'm +1.
17:07 <ogasawara> ..
17:08 <kamal> +1 from me
17:08 <henrix> +1 from me too!
17:08 <arges> From an SRU perspective, sforshee has generally shown attention to detail. The debdiffs I've reviewed have been free of cruft and look good. +1
17:08 * smb would +1 as well despite being no sponsor either
17:08 * apw has worked with him on a number of packages and feel he has the appropriate level of fear and self doubt: +1
17:08 <bjf> +1
17:08 <cking> +1
17:09 * apw counts ... that appears to be +1 from all present approvers and a slew of additional approvals
17:09 <apw> sforshee, welcome to the team
17:09 <sforshee> thanks all!
17:09 <cking> \o/
17:09 <henrix> \o/
17:09 <apw> thank you ...
17:09 <kamal> \o/
17:09 <ogasawara> congrats sforshee!
17:09 <arges> good job
17:09 <apw> jsalisbury, all yours ...
17:09 <jsalisbury> apw, thanks.  and congrats to sforshee
17:10 <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
17:10 <jsalisbury> Thanks everyone
17:10 <jsalisbury> #endmeeting