[13:13] <JHOSMAN> Good morning mhall119
[13:19] <mhall119> JHOSMAN: good morning, your request was approved, you should get an email today
[13:20] <JHOSMAN> mhall119: Excelent! :D
[13:21] <JHOSMAN> excellent, you tell me that I can forward to you to arrange sponsorship money? mhall119
[13:22] <JHOSMAN>  The event is in 11 days.
[13:24] <mhall119> JHOSMAN: like I said, you should get an email from msm who will coordinate that with you
[13:26] <JHOSMAN> mhall119: Fine, then I'll wait notification from you, on the other hand we talked about that if they wish they could put a big banner of Ubuntu but we talked about two options, the first being that you send us a banner and come back by return mail the second (more economical for you and us) is print here in Colombia and that stay here (this cost would be borne by you. (canonical)
[16:00] <coreycb> o/
[16:00] <coreycb> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Apr  7 16:00:17 2015 UTC.  The chair is coreycb. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <beisner> o/
[16:00] <rharper> o/
[16:00] <matsubara> o/
[16:00] <caribou> o/
[16:00] <smb> o/
[16:00] <strikov> o/
[16:00] <coreycb> Hello everone and welcome to the weekly ubuntu-server meeting
[16:00] <coreycb> #topic Review ACTION points from previous meeting
[16:01] <coreycb> there was one action item from last week - James Page to provide feedback on bugs 1425288 and 1425128
[16:01] <smb> I do not recall any updates there
[16:01] <coreycb> ok smb, and jamespage is likely busy as he is sprinting
[16:01] <coreycb> I'll keep this one as an action
[16:02] <coreycb> #action James Page to provide feedback on bugs 1425288 and 1425128
[16:02] <meetingology> ACTION: James Page to provide feedback on bugs 1425288 and 1425128
[16:02] <smb> ok, though so will I next week (sprinting) ;)
[16:02] <coreycb> sigh
[16:02] <coreycb> #topic Vivid Development
[16:02] <coreycb> #link https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[16:03] <coreycb> we're past final beta freeze  and the next milestone is kernel freeze on April 9th.  final freeze is April 16th.  release of 15.04 is April 23rd.
[16:04] <coreycb> #subtopic Release Bugs
[16:04] <coreycb> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:05] <coreycb> no new bugs since last week
[16:05] <coreycb> dannf, anything new on 1427406?
[16:06] <coreycb> smoser, anything new on 1427275?
[16:07] <coreycb> juju team is actively working on 1409639
[16:08] <coreycb> and looks like utlemming is actively working on 1409639
[16:09] <coreycb> ok let's move on
[16:09] <coreycb> #subtopic Blueprints
[16:09] <coreycb> #link http://status.ubuntu.com/ubuntu-v/group/topic-v-server.html
[16:10] <coreycb> this should be a bit greener at this point in the cycle so please update your progress
[16:10] <coreycb> #link https://blueprints.launchpad.net/ubuntu/+spec/topic-v-server
[16:11] <coreycb> and we should likely start deferring things soon
[16:11] <coreycb> #topic Server & Cloud Bugs (caribou)
[16:11] <caribou> coreycb: nothing particular this week, thanks
[16:11] <coreycb> thanks caribou
[16:12] <coreycb> #topic Weekly Updates & Questions for the QA Team (matsubara)
[16:12] <matsubara> Nothing new to report. Most of the smoke tests are still failing and I'm not doing a very good job at babysitting them
[16:13] <coreycb> matsubara, ok, thanks and good luck with those
[16:13] <coreycb> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:13] <smb> Nothing specific this week. Just repeating as a reminder that UE is sprinting next week, so there is a high chance I might miss next weeks irc meeting (and probably same for arges and sforshee )
[16:13] <coreycb> smb, ok thanks for the update
[16:14] <coreycb> #topic Ubuntu Server Team Events
[16:14] <coreycb> any events going on?  I know there are a few sprints going on.
[16:15] <coreycb> #topic Open Discussion
[16:15] <coreycb> does anyone have anything else they'd like to cover?
[16:15] <coreycb> thanks everyone for attending
[16:15] <coreycb> #topic Announce next meeting date, time and chair
[16:16] <beisner> thx coreycb
[16:16] <caribou> thanks coreycb
[16:16] <dannf> coreycb: i provided a patch
[16:16] <coreycb> Tues April 14th 16:00 UTC
[16:16] <dannf> coreycb: in that bug
[16:16] <coreycb> dannf, ah ok
[16:16] <dannf> coreycb: still blocked on the mariadb side
[16:17] <dannf> coreycb: but as for mysql, i'm considering it done from my pov unless someone asks for something
[16:18] <coreycb> dannf, ok do you need anything from the server team?
[16:18] <dannf> coreycb: review/upload i guess :)
[16:19] <dannf> and testing on non-arm64, if you have tests to run
[16:19] <coreycb> rbasak, can you handle that?
[16:20] <dannf> (and happy to help where i can, not trying to throw it over the wall... completely) :)
[16:20] <coreycb> dannf, I'll add an action for rbasak since he had asked for a patch in that bug
[16:21] <rbasak> o/
[16:21] <rbasak> dannf: I thought the patch wasn't ready to upload to Ubuntu yet?
[16:21] <rbasak> If so, I don't feel I have any action I can take here.
[16:22] <rbasak> I'd prefer to see the patch adopted upstream - then we can certainly update or cherry-pick it.
[16:22] <dannf> rbasak: i'd like upstream to ack it, but they haven't. it's definitely *better* on arm64 than the current version, but i don't have regression tests for other archs
[16:23] <rbasak> We can't risk regression on other archs
[16:23] <strikov> dannf: do you mean the whole series of patches or just the last one which adds aarch64 to power-related ifdefs?
[16:23] <dannf> strikov: entire series
[16:24] <dannf> rbasak: right - and is there a way we can regression test other archs in house?
[16:24] <rbasak> Beyond the standard test suite? Not that I'm aware of.
[16:24] <rbasak> But this kind of fix strikes me as the type that standard regression tests won't catch.
[16:26] <rbasak> I guess what I'm expecting is someone to go deep and verify, in whatever way necessary, to a reasonable level that there won't be a regression on another arch.
[16:26] <coreycb> thanks for the discussion guys.  I"m going to end the meeting.  I assume you can continue the discussion offline if needed.
[16:26] <rbasak> OK, that's fair. Thanks coreycb.
[16:26] <coreycb> #endmeeting
[16:26] <meetingology> Meeting ended Tue Apr  7 16:26:59 2015 UTC.
[16:26] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-07-16.00.moin.txt
[16:28] <dannf> rbasak: yeah, and I don't think I'm capable of that - so i guess that means blocked-on-upstream-acceptance?
[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 Apr  7 17:00:17 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] <arges> o/
[17:00] <henrix> o/
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <kamal> o/
[17:00] <ogasawara> o/
[17:00] <rtg> o/
[17:00] <sforshee> o/
[17:00] <smb> \o
[17:00] <cking> o/
[17:00] <bjf> o/
[17:00] <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] <ogasawara> Our Vivid kernel remains based on the upstream v3.19.3 stable kernel.
[17:01] <ogasawara> Vivid kernel freeze is this Thurs Apr 9.  We are still chasing down some
[17:01] <ogasawara> recent regressions, but we intend to prepare and upload our proposed
[17:01] <ogasawara> final kernel for Vivid no later than tomorrow Wed Apr 8.  If you have
[17:01] <ogasawara> any patches which need to land for 15.04's release, please let us know
[17:01] <ogasawara> and get them submitted to the list now.
[17:01] <ogasawara> -----
[17:01] <ogasawara> Important upcoming dates:
[17:01] <ogasawara> [LINK] https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[17:01] <ogasawara> Thurs Apr 09 - Kernel Freeze (~2 days away)
[17:01] <ogasawara> Thurs Apr 23 - 15.04 Release (~2 weeks away)
[17:01] <ogasawara> ..
[17:01] <jsalisbury> [TOPIC] Status: CVE's
[17:01] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:01] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)
[17:01] <bjf> Status for the main kernels, until today:
[17:02] <bjf>   *   Lucid - None (no update)
[17:02] <bjf>   * Precise - Testing & Verification
[17:02] <bjf>   *  Trusty - Testing & Verification
[17:02] <bjf>   *  Utopic - Testing & Verification
[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] <bjf>  
[17:02] <bjf> NOTE: Lucid goes EOL on April 30.
[17:02] <bjf>  
[17:02] <bjf> ..
[17:02] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:02] <jsalisbury> Thanks everyone
[17:02] <jsalisbury> #endmeeting
[17:02] <meetingology> Meeting ended Tue Apr  7 17:02:56 2015 UTC.
[17:02] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-07-17.00.moin.txt
[17:03] <kamal> thanks jsalisbury
[17:29] <dkessel> hey costales: good job on anoise! i enjoy it :)