[01:34] <fghgf> hm..
[07:27] <dholbach> good morning
[16:00] <beisner> o/
[16:00] <hallyn> \o
[16:00] <rbasak> o/
[16:00] <caribou> o/
[16:00] <hallyn> morning everyone
[16:00] <smb> o/
[16:00] <hallyn> let's get started
[16:01] <hallyn> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Oct 28 16:01:01 2014 UTC.  The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: action commands idea info link nick
[16:01] <coreycb_> o/
[16:01] <hallyn> #topic Review ACTION points from previous meeting
[16:01] <hallyn> none
[16:01] <hallyn> #topic Vervet development
[16:01] <matsubara> o/
[16:01] <hallyn> smoser: jamespage: wanna take this away?
[16:02] <smoser> shoudln't it be vivid ?
[16:02] <hallyn> uh, yeah
[16:02] <smoser> sure. anyway.
[16:02] <hallyn> hm, think i got that wrong ina  changelog this mroning
[16:02] <smoser> right now, we're clearly just starting with this vivid thing.
[16:02] <smoser> and hallyn is catching up
[16:02] <smoser> so development at this point would consist of merging from debian, and thinking of feature development / work for the cycle.
[16:03] <smoser> and getting blue prints together.
[16:03] <hallyn> any timeline for blueprint creation?
[16:04] <hallyn> smoser:
[16:04] <smoser> i dont know actually. i'm not that far along.
[16:04] <hallyn> ok
[16:04] <hallyn> thanks
[16:05] <hallyn> #topic Server & Cloud Bugs (caribou)
[16:05] <caribou> nothing particular from our side
[16:05] <caribou> any question ?
[16:05] <hallyn> sounds like no, thanks caribou.  moving on,
[16:05] <hallyn> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:06] <hallyn> psivaa_: anything for the server meeting today?
[16:06] <hallyn> sounds like no, moving on,
[16:06] <hallyn> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:07] <smb> nothing from here today
[16:07] <hallyn> thanks smb
[16:07] <hallyn> #topic Ubuntu Server Team Events
[16:07] <hallyn> we've got ODS next week of course,
[16:07] <hallyn> anything else?
[16:07] <rbasak> UOS is coming up too.
[16:07] <hallyn> good point.  and when is that?
[16:08] <hallyn> nov 12
[16:08] <hallyn> http://summit.ubuntu.com/uos-1411/
[16:08]  * rbasak can't find the reminder email he just received
[16:08] <rbasak> Ah, thanks.
[16:08] <rbasak> It's be good to get any blueprint level items agreed before UOS, so we can make decisions during UOS itself instead of endless debate.
[16:08] <hallyn> ok i see that disucssing EOLing of machine type sis still on teh agenda, but as i recall it was decided that should be brought up on the m-l instead,
[16:09] <hallyn> #action hallyn to discuss machine type EOLing on ubuntu-server m-l
[16:09] <meetingology> ACTION: hallyn to discuss machine type EOLing on ubuntu-server m-l
[16:09] <smoser> thank you rbasak
[16:09] <hallyn> rbasak: should we do some semi-organized thing where we email proposed blueprints to the mailing list?
[16:09] <rbasak> That's a good idea.
[16:10] <hallyn> ok, let's codify that,
[16:10] <hallyn> #action everyone to email blueprint proposals to mailing list for discussion
[16:10] <meetingology> ACTION: everyone to email blueprint proposals to mailing list for discussion
[16:10] <hallyn> thanks, moving on,
[16:10] <hallyn> #topic Open Discussion
[16:10] <rbasak> Juju 1.20 will be hitting Trusty in an SRU soon.
[16:11] <hallyn> compeltely backward-compat??
[16:11] <rbasak> This is a major version update, so I'd encourage everyone using Juju to test the upload when it arrives in trusty-proposed, and let us know of any regressions.
[16:11] <rbasak> Yes, it should be fully compatible.
[16:11] <hallyn> perhaps we should have an agenda item for next week to ask who's been testing?
[16:11] <rbasak> You might want to update your deployment, but that's up to you.
[16:11] <rbasak> I'm tracking testing in the bug - bug 1386144.
[16:11] <hallyn> oh, but are we having a meeting next week, or will everyoen be gone for ods
[16:12] <hallyn> rbasak: sounds good
[16:12] <rbasak> Probably not worth having a meeting next week?
[16:12] <hallyn> yeah let's skip to the next week
[16:12] <hallyn> any other items for open discussion
[16:12] <rbasak> Next week a bunch of Canonicalers will be at a sprint
[16:12] <rbasak> Oh, no, that's the week after.
[16:12] <rbasak> Sorry.
[16:13] <hallyn> ok, so moving on,
[16:13] <hallyn> #topic Announce next meeting date, time and chair
[16:13] <hallyn> Should be in two weeks, Tuesday Nov 11 2014, 16:00 utc as usual,
[16:13] <hallyn> matsubara will be chairing
[16:13] <hallyn> thanks everyeone,
[16:13] <hallyn> #endmeeting
[16:13] <meetingology> Meeting ended Tue Oct 28 16:13:56 2014 UTC.
[16:13] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-28-16.01.moin.txt
[16:13] <matsubara> ok. thanks hallyn
[16:13] <rbasak> Thanks hallyn!
[16:14] <beisner> thanks hallyn
[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 Oct 28 17:00:02 2014 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/Utopic
[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] <kamal> o/
[17:00] <henrix> o/
[17:00] <sforshee> o/
[17:00] <arges> o/
[17:00] <bjf> o/
[17:00] <ppisati> o/
[17:01] <cking_> o/
[17:02] <rtg> o/
[17:02] <smb> o/
[17:02] <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:03] <jsalisbury> [TOPIC] Status: Vivid Development Kernel (ogasawara)
[17:06] <jsalisbury> [TOPIC] Status: CVE's
[17:06] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:06] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:06] <jsalisbury> ..
[17:07] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)
[17:07] <bjf> Status for the main kernels, until today (Sept. 30):
[17:07] <bjf>   *   Lucid -
[17:07] <bjf>   * Precise -
[17:07] <bjf>   *  Trusty - Testing
[17:07] <bjf>  
[17:07] <bjf> Current opened tracking bugs details:
[17:07] <bjf>   * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
[17:07] <bjf> For SRUs, SRU report is a good source of information:
[17:07] <bjf>   * http://kernel.ubuntu.com/sru/sru-report.html
[17:07] <bjf>  
[17:07] <bjf>  
[17:07] <bjf> Schedule:
[17:07] <bjf>  
[17:07] <bjf> cycle: 10-Oct through 31-Oct
[17:07] <bjf> [17:07] <bjf>           8-Oct   Last day for kernel commits for this cycle
[17:07] <bjf>           09-Oct - 10-Oct   Kernel prep
[17:07] <bjf>           12-Oct - 18-Oct   Bug verification & Regression testing.
[17:07] <bjf>           19-Oct - 25-Oct   Bug verification & Regression testing.
[17:07] <bjf>           26-Oct - 01-Nov   Regression testing & Release to -updates.
[17:07] <bjf>  
[17:07] <bjf> ..
[17:08] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:08] <jsalisbury>  Vivid Development Kernel update will be added to the minutes posted on the wiki/blog.
[17:09] <jsalisbury> Thanks everyone
[17:09] <jsalisbury> #endmeeting
[17:09] <meetingology> Meeting ended Tue Oct 28 17:09:54 2014 UTC.
[17:09] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-28-17.00.moin.txt
[17:10] <kamal> thanks jsalisbury