[15:30] <beisner> o/
[15:35] <beisner> oh, i'm 30 minutes early.
[15:35]  * beisner goes back to work
[15:58] <kickinz1> o/
[15:59] <beisner> o/   hey kick!
[15:59] <matsubara> o/
[16:00] <smoser> o/
[16:00] <rbasak> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Mar 24 16:00:06 2015 UTC.  The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <rbasak> #topic Review ACTION points from previous meeting
[16:00] <rbasak> everyone look at server guide and look for areas which need updating
[16:00] <gaughen> 0/
[16:00] <strikov> 0/
[16:01] <rbasak> I'm not sure what further action to take here, apart from reminding everyone to do this.
[16:01] <rbasak> hallyn to talk with dannf about bug 1427406
[16:01] <gnuoy> o/
[16:01] <rbasak> This one has been assigned to me, but I don't really have any action to take unless someone can present a patch.
[16:01] <zul> hi
[16:02] <rbasak> If it's MySQL upstream related, then trying ryeng on #debian-mysql on OFTC may be helpful.
[16:02] <hallyn> dannf: says he can look at it in a few days (i believe)
[16:02] <hallyn> otherwise i can try to look deeper next week.  but i'm really out o fmy element there
[16:02] <dannf> hallyn, rbasak - yes, which will likely start with me asking upstream
[16:02] <rbasak> OK. I'll unassign for now.
[16:03] <rbasak> hallyn to look at bug 1432715
[16:03] <hallyn> it's present in debian as well
[16:04] <hallyn> the debian bug hopes to post a fix over the weekend
[16:04] <gnuoy> o/
[16:04] <hallyn> (of course that was last weekend)
[16:05] <rbasak> hallyn to update QA Team section assignee to matsubara
[16:05] <hallyn> done
[16:05] <rbasak> matsubara to file a bug for libpam-systemd's dependency problem
[16:05] <jamespage> o/
[16:05] <jamespage> late as usual - sorry
[16:05] <matsubara> rbasak, I filed bug 1433190 but that's been invalidated
[16:06] <matsubara> rbasak, and the smoke tests are not failing anymore with that error
[16:06] <rbasak> matsubara: OK, it should be safe to leave it then? Thanks.
[16:06] <matsubara> they are failing for other reasons now which I'll raise in the QA section
[16:06] <matsubara> yep, I think so
[16:06] <rbasak> OK
[16:06] <rbasak> #topic Vivid Development
[16:06] <rbasak> #link https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[16:06] <rbasak> #subtopic Release Bugs
[16:06] <rbasak> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:07] <rbasak> Anything in that list that needs discussion?
[16:08] <rbasak> #subtopic Blueprints
[16:08] <rbasak> #link http://status.ubuntu.com/ubuntu-v/group/topic-v-server.html
[16:08] <rbasak> #link https://blueprints.launchpad.net/ubuntu/+spec/topic-v-server
[16:08] <rbasak> Any blueprints that need discussion?
[16:09] <rbasak> caribou is out this week, so we'll skip the Server and Cloud Bugs topic unless anyone else wants to step up?
[16:09] <rbasak> #topic Weekly Updates & Questions for the QA Team (matsubara)
[16:09] <matsubara> rbasak, some smoke tests are failing due to a UTAH time out
[16:10] <matsubara> for example http://d-jenkins.ubuntu-ci:8080/job/vivid-server-amd64-smoke-dns-server/113/console
[16:10] <matsubara> in general the test pass, so I think this is due to failure to reach the archive (scroll up in that console log)
[16:10] <rbasak> #link https://jenkins.qa.ubuntu.com/job/vivid-server-amd64-smoke-dns-server/113/console
[16:11] <matsubara> not sure if there's an action here other than keeping looking at the logs and see if any of those are real failures
[16:11] <rbasak> matsubara: can you request a retest?
[16:12] <matsubara> I don't seem to have that permission
[16:12] <rbasak> It certainly does look like a test environment connectivity issue to me.
[16:12] <rbasak> matsubara: shall we leave it to you to get a message to the right person to request a retest?
[16:12] <rbasak> Let's move on for now.
[16:12] <rbasak> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:12] <matsubara> rbasak, ok
[16:12] <matsubara> thanks rbasak
[16:12] <smb> The Utopic+ nested issues on Precise host fix should be on its way into Precise. Beside that any other reports are still ongoing. There were recent updates to nested kvm softlockups (bug 1413540) and some container netdevice cleanup (bug 1403152) bug which we still need to evaluate. The KSM issue (bug 1435363) which was recently reported needs feedback on latest kernel.
[16:13] <rbasak> Thanks. Any questions for smb?
[16:13] <rbasak> Any other discussion on this topic?
[16:14] <rbasak> #topic Ubuntu Server Team Events
[16:14] <rbasak> I'm not aware of anything coming up. Does anyone have any events to add?
[16:14] <rbasak> #topic Open Discussion
[16:14] <rbasak> Anything else from anyone before we close?
[16:15] <rbasak> #topic Announce next meeting date and time
[16:15] <rbasak> The next meeting will be at Tue Mar 31 16:00:00 UTC 2015. matsubara will be chairing.
[16:16] <rbasak> Thanks all!
[16:16] <rbasak> #endmeeting
[16:16] <meetingology> Meeting ended Tue Mar 24 16:16:04 2015 UTC.
[16:16] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-24-16.00.moin.txt
[16:16] <matsubara> thanks rbasak
[16:16] <beisner> thanks, rbasak
[16:18] <kickinz1> thanks
[16:30] <hallyn> j/wc
[17:00] <jsalisbury> #startmeeting
[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] <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> Available commands: action commands idea info link nick
[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] <apw> o/
[17:00] <henrix> 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
[17:10] <meetingology> Meeting ended Tue Mar 24 17:10:33 2015 UTC.
[17:10] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-24-17.00.moin.txt
[17:10] <kamal> thanks jsalisbury!