[15:56] <kickinz1> o/
[15:58] <hallyn> o/
[16:00] <kickinz1> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Jan  6 16:00:09 2015 UTC.  The chair is kickinz1. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:01] <kickinz1> #topic Review ACTION points from previous meeting
[16:01] <coreycb> o/
[16:01] <matsubara> o/
[16:01] <kickinz1> seems there is an action point, seems done right?
[16:03] <kickinz1> SO I go to Vivid dev?
[16:03] <coreycb> kickinz1, you may want to paste the action point.  I'm not seeing logs from the last meeting.
[16:04] <kickinz1> ok
[16:04] <kickinz1> Review ACTION points from previous meeting
[16:04] <kickinz1> matsubara to chase someone that can update release bugs report: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:04] <kickinz1> I filed https://bugs.launchpad.net/ubuntu-qa-website/+bug/1398443 for this, which has been fixed by Brian Murray and the report now works -- 2014-12-02 matsubara
[16:04] <arges> o/
[16:04] <gaughen> o/
[16:04] <matsubara> kickinz1, that's been sorted out in the previous meeting
[16:04] <kickinz1> sorry..
[16:05] <kickinz1> #topic Vivid Development
[16:05] <hallyn> kickinz1: not your fault, last person should have updated it.  please do so this time
[16:05] <kickinz1> ok I'll  do
[16:05] <hallyn> thanks :)
[16:05] <kickinz1> So anything related to vivid?
[16:06] <hallyn> I need to talk to stgraber but it loks like we're going to track lxd through github milestones/issues rather than blueprint
[16:06] <kickinz1> https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[16:07] <kickinz1> #link https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[16:07] <coreycb> that tag may be broken, we can look at the url on our own
[16:07] <gaughen> sorry kickinz1 I think that was me that should have updated the action, and I actually thought I did
[16:08] <gaughen> our next big date for the release is feature freeze - Feb 19
[16:08] <coreycb> or maybe link isn't supposed to do anything (ignore me)
[16:08] <kickinz1> the #link is in the command list...
[16:09] <kickinz1> #subtopic Release Bugs
[16:09] <kickinz1> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:10] <kickinz1> #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:12] <gaughen> maybe the meeting tool doesn't like a french '#' kickinz1 ;-)
[16:13] <gaughen> coreycb, kickinz1 is that link working for you? I'm getting a blank page
[16:13] <coreycb> it's dead for me
[16:13] <gaughen> anyhow, I'm not aware of any major show stoppers right now, so we can move on to blueprints
[16:13] <kickinz1> So link doesn't work, replacing reqorts by reports doesn't seem do to anything, I'll look into ot after
[16:13] <gaughen> although I would say one thing on my mind is the move to systemd this cycle
[16:14] <gaughen> we need to carve out some time to make sure the services that are server image specific are  happy
[16:14] <gaughen> and we need to do that this month
[16:14] <gaughen> anyhow, kickinz1 you can move us along with your fancy french #s ;-)
[16:14] <kickinz1> ok
[16:15] <kickinz1> #subtopic Blueprints
[16:15] <kickinz1> #link http://status.ubuntu.com/ubuntu-v/group/topic-v-server.html
[16:15] <gaughen> kickinz1, I've been trying to make sure our blueprints are in a good state. as usual they need love. But I will continue to work that.
[16:16] <gaughen> and as hallyn mentioned the plan will be to track lxd not in blueprints but on github
[16:16] <kickinz1> ok
[16:16] <gaughen> smoser, we need to get a cloud-init blueprint in shape for the python3 rebase
[16:16] <gaughen> anyhow, that is all kickinz1
[16:16] <smoser> gaughen, agreed.
[16:17] <kickinz1> So going to SErver and Cloud
[16:17] <kickinz1> #topic Server & Cloud Bugs (caribou)
[16:17] <gaughen> it worked kickinz1!
[16:17] <caribou> kickinz1: nothing particular here
[16:17] <kickinz1> ok
[16:17] <kickinz1> thanks caribou
[16:17] <kickinz1> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:18] <kickinz1> psivaa_ ?
[16:19] <kickinz1> So next
[16:19] <kickinz1> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:19] <arges> the kernel is perfect and no bugs exist. : )
[16:19] <kickinz1> :)
[16:20] <beisner> kickinz1, plz add action item for me:   establish new qa-team point of contact for server team
[16:20] <arges> feel free to let us know of any issues as usual
[16:20] <psivaa_> kickinz1: sorry i am no longer in the QA team. besigner was inthe process of finding a QA rep
[16:20] <kickinz1> ok thanks psivaa_
[16:21] <kickinz1> thanks arges
[16:21] <kickinz1> #topic Ubuntu Server Team Events
[16:22] <kickinz1> So any Ubuntu Server Team Events coming soon?
[16:22] <gaughen> well jamespage's birthday is coming up
[16:22] <gaughen> for real this time
[16:22] <kickinz1> A new team member with the nickname tmoser ?
[16:22] <gaughen> kickinz1, yes!
[16:23] <gaughen> kickinz1, but otherwise I'm not aware of any upcoming events.
[16:23] <kickinz1> ok I move on
[16:23] <kickinz1> #topic Open Discussion
[16:23] <kickinz1> Anyone?
[16:24] <kickinz1> #topic Announce next meeting date and time
[16:24] <kickinz1> So next meeting is 13 jan 2015
[16:25] <kickinz1> next chair is smoser
[16:25] <kickinz1> #endmeeting
[16:25] <meetingology> Meeting ended Tue Jan  6 16:25:19 2015 UTC.
[16:25] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-01-06-16.00.moin.txt
[16:25] <kickinz1> thanks all, and sorry foir the lag...
[16:25] <coreycb> thanks kickinz1!
[16:26] <smoser> next share surely isn't me.
[16:26] <smoser> i must didn't do my updating. :-(
[16:26] <beisner> thanks kickinz1 !
[16:27] <gaughen> smoser, the rotation seems to go very very fast
[16:27] <gaughen> kickinz1, thanks!
[16:27] <kickinz1> I think he replaces me last time, so maybe it is too fast.
[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] <meetingology> Meeting started Tue Jan  6 17:00:22 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> [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/  2015 already
[17:00] <bjf> o/
[17:00] <henrix> o/
[17:00] <arges> o/
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[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] <jsalisbury> Both the master and master-next branches of our Vivid kernel have been
[17:01] <jsalisbury> rebased to the v3.18.1 upstream stable kernel.  We have also uploaded
[17:01] <jsalisbury> our first 3.18 based kernel to the archive (3.18.0-8.9).  Please test and let us
[17:01] <jsalisbury> know your results.  We are also starting to track the v3.19 kernel on
[17:01] <jsalisbury> our unstable branch.
[17:01] <jsalisbury> -----
[17:01] <jsalisbury> Important upcoming dates:
[17:01] <jsalisbury> [LINK] https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[17:01] <jsalisbury> Fri Jan 9 - 14.04.2 Kernel Freeze (~3 days away)
[17:01] <jsalisbury> Thurs Jan 22 - Vivid Alpha 2 (~2 weeks away)
[17:02] <jsalisbury> Thurs Feb 5 - 14.04.2 Point Release (~4 weeks away)
[17:02] <jsalisbury> Thurs Feb 26 - Beta 1 Freeze (~7 weeks away)
[17:02] <jsalisbury> ..
[17:02] <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 - Verification & Testing
[17:02] <bjf>   * Precise - Verification & Testing
[17:02] <bjf>   *  Trusty - Verification & Testing
[17:02] <bjf>   *  Utopic - Verification & Testing
[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> cycle: 12-Dec through 10-Jan
[17:02] <bjf> [17:02] <bjf>          12-Dec   Last day for kernel commits for this cycle
[17:02] <bjf> 14-Dec - 20-Dec   Kernel prep week.
[17:02] <bjf> 21-Dec - 10-Jan   Bug verification; Regression testing; Release
[17:02] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <jsalisbury> Thanks everyone
[17:03] <jsalisbury> #endmeeting
[17:03] <meetingology> Meeting ended Tue Jan  6 17:03:54 2015 UTC.
[17:03] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-01-06-17.00.moin.txt
[17:04] <cking> thanks jsalisbury