/srv/irclogs.ubuntu.com/2015/06/16/#ubuntu-meeting.txt

=== pgraner-dr is now known as pgraner
=== davidcalle_ is now known as davidcalle
arosaleszul, looks like you chaired last week correct?16:00
smosero/16:01
tewardo/16:01
jamespageo/16:01
smbo/16:01
hallyn\o16:01
matsubarao/16:01
* arosales guessing zul chaired last week and its my turn16:01
hallynthen zul didn't update the page16:01
caribouo/16:02
arosales#startmeeting ubuntu-server-team16:02
meetingologyMeeting started Tue Jun 16 16:02:18 2015 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:02
meetingologyAvailable commands: action commands idea info link nick16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic:
beisnero/16:02
arosales#topic Review ACTION points from previous meeting16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Review ACTION points from previous meeting
* arosales doesn't see any action items from the previous meeting16:02
arosales#topic Vivid Development16:02
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Vivid Development
arosales#link https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule16:03
arosales#info Alpha 1 coming up June 2516:03
coreycbo/16:03
arosales#subtopic Release Bugs16:03
arosales#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server16:04
* arosales trying to pull up http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server . . . 16:04
arosalesis that URL working for others?16:04
tewardarosales: site death perhaps, the white page of death16:04
tewardoh wait16:04
rharper\o16:05
tewardnope16:05
tewardwpod, still, arosales16:05
tewardi think it's down16:05
arosalesjust whit page for me16:05
caribouwpod for me16:05
arosales*white16:05
beisner:-/  0k file16:05
tewardarosales: codenamed: "White Page Of Death" - WPOD16:05
tewardcontact canonical sysadmins for fixing?16:05
rharperbeisner: indeed16:05
arosalesteward, ack, WPOD it seems16:05
arosalesrharper, can you take that action?16:05
rharperarosales: sure16:06
arosales#action rharper to follow up with canonical sysadmins on  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server WPOD16:06
meetingologyACTION: rharper to follow up with canonical sysadmins on  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server WPOD16:06
arosalesthanks rharper16:06
arosalesany bugs folks would like to discuss before moving on16:06
arosalesI'll take it folks are ready for BPs then16:07
arosales. . .16:07
arosales#subtopic Blueprints16:07
arosales#link http://status.ubuntu.com/ubuntu-w/group/topic-w-server.html16:07
arosaleshttp://status.ubuntu.com/ubuntu-w/group/topic-w-server.html   not working for me either today16:07
tewardarosales: confirmed, 404.16:08
arosaleswe have http://status.ubuntu.com/ubuntu-w/group/topic-w-openstack.html16:08
arosalesbut not server16:08
arosalesrharper, smoser: do you guys have a topic BP?16:08
smoserchecking. i dont think we probably do.16:09
smoseror i do not think we do16:10
matsubaraarosales, http://status.ubuntu.com/ubuntu-w/canonical-server.html and http://status.ubuntu.com/ubuntu-w/ubuntu-server.html might give a better overview of server BPs16:10
matsubarasince the topic url is not working...16:10
arosalesmatsubara, ok, do folks agree here we should update the meeting commands to these links?16:11
* matsubara doesn't really know what's more appropriate in this case16:11
arosales#action smoser update Topic blueprint URLs, if necessary16:11
meetingologyACTION: smoser update Topic blueprint URLs, if necessary16:11
arosales#link http://status.ubuntu.com/ubuntu-w/canonical-server.html16:12
arosaleshttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-w-openstack-liberty progressing16:12
arosalessorry16:13
arosales#link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-w-openstack-liberty16:13
arosales#link http://status.ubuntu.com/ubuntu-w/ubuntu-server.html16:13
arosalessame blueprint there16:13
arosalesand as said before servercloud-w-openstack-liberty is progressing16:14
arosalesbut seems there should be some other BPs there . .  .16:14
arosalessmoser, jamespage need to follow up if the correct BPs are linked  ^16:14
arosalesperhaps because https://blueprints.launchpad.net/ubuntu/+spec/topic-w-server is blank atm ?16:15
arosales#link https://blueprints.launchpad.net/ubuntu/+spec/topic-w-server16:15
arosalesin any case an action item is made to follow up.16:15
arosalesPing here if folks have any BPs items they would like to surface16:16
arosales. . .16:16
arosalesmoving on16:16
arosales#topic Server & Cloud Bugs (caribou)16:16
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Server & Cloud Bugs (caribou)
caribounothing major to me; mostly done with rsyslog merge16:16
arosalescaribou, thanks for the update16:16
arosales#topic Weekly Updates & Questions for the QA Team (matsubara)16:16
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the QA Team (matsubara)
matsubaraarosales, nothing new to report16:16
arosalesmatsubara, ok, thanks16:17
arosales#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:17
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
smbI have nothing today if nobody else has anything.16:17
arosalesany questions for smb (kernel)?16:17
arosales. . .16:17
arosales#topic Ubuntu Server Team Events16:17
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Ubuntu Server Team Events
arosalesIf any folks are interested in Spark. I am currently at Spark Summit and we'll be hosting an even tonight16:18
arosaleshttps://insights.ubuntu.com/event/big-data-mine-and-mingle/16:18
arosalessorry16:18
arosales#link https://insights.ubuntu.com/event/big-data-mine-and-mingle/16:18
arosalesany others?16:18
arosales. . .16:18
arosales#topic Open Discussion16:18
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Open Discussion
arosalesother items?16:18
tewardi think there's a missing item16:18
tewardwhich agenda page are you using, the ServerTeam/Meeting one?16:19
arosalesteward, using https://wiki.ubuntu.com/ServerTeam/Meeting/IRCCommands16:19
arosaleslinked from https://wiki.ubuntu.com/ServerTeam/Meeting16:19
arosalesteward, was there another topic?16:19
tewardarosales: there's an item on the Agenda page added by me, and I'd like Server Team input on the course of action16:19
tewardarosales: https://wiki.ubuntu.com/ServerTeam/Meeting - NGINX in Ubuntu: Course of Action discussion (teward)16:19
tewardpopped on in the middle of last week16:20
arosalesteward, ahh, sorry for missing that16:20
tewardperhaps it was missed?16:20
tewardno problem :)16:20
arosales#link https://lists.ubuntu.com/archives/ubuntu-server/2015-June/007072.html16:20
tewardPreviously, up until now, Debian was using a Stable branch of the NGINX web server's code as the package base.16:21
tewardRecently, based on what they do with Debian release times as far as I can gather, they're now using an NGINX Mainline branch, which is their feature-development branch.16:21
tewardFurther questions on that branch can be directed to LinuxJedi who is here currently, and is a Senior Developer Advocate for the nginx upstream people16:22
LinuxJedio/16:22
tewardCurrently, as of 15.04, we are using the Stable branch of NGINX in Ubuntu, which is mirroring Debian's choice of package versions.  However, following them will have Wily get 1.9.1 currently, which will likely remain that way through next LTS16:22
tewardWhile both versions are 'stable' enough to be used in production environments, and indeed I do have a couple Mainline nginx versions running in production, that is a changing development branch, replete with new features.16:23
teward1.8.x is the NGINX Stable branch, which receives critical bug fixes and security updates but forgoes the additional features.16:23
hallynyou expect a stable branch of the current devel branch by 16.02 ?16:24
tewardhallyn: from what LinuxJedi has told me, such release (1.10.x) will be very near or after FinalFreeze or release date for LTS16:24
hallynthat's unfortunate :)16:24
LinuxJedibut there shouldn't be much change from 1.9.x to 1.10.0 at that stage16:25
tewardthey release the 'mainline' as stable in April, and judging by the last release date, April 21, on or near that date would put us really close to release date16:25
hallynbut if we could get a 1.10.alpha1 that might be good.  i assume the stable releases will be supported much longer than devel16:25
hallyni think it's worth asking the release time for best option there16:25
tewardTo finish my initial thought stream: I'd like the Server Team to provide some guidance for Wily, as to how we proceed16:26
hallynhm, no rbasak today16:26
tewardA merge of 1.9.1 wouldn't take too long.  Merging in changes from Debian's packaging and merging that with 1.8.x is doable by myself, but would diverge from the standard process of getting packaging from Debian16:26
hallynyou already emailed ubntu-server about this right?16:27
tewardhallyn: indeed.  I did ask Seth Arnold (sarnold) for his opinions, he responded to the email thread on the server mailing list16:27
smoserteward, well, the questions hallyn asked apply for wily as well as x (16.04)16:27
hallynright,16:27
tewardhallyn: the email link that arosales posted.16:27
tewardsmoser: indeed.16:27
tewardhttps://lists.ubuntu.com/archives/ubuntu-server/2015-June/007072.html16:27
smoserwe dont want to move forward in wily if we would then have to move back.16:27
hallyni'd follow sarnold's guidance :)16:27
hallynteward: how long do you expect 1.9 to be supported?16:27
LinuxJediit is worth noting that useful LTS features such as HTTP/2 will be in 1.1016:27
tewardhallyn: doing so would place us on 1.9.x.16:27
tewardhallyn: until 1.10.x release in April, I believe.  LinuxJedi: that's the upstream support period, if I'm not mistaken?16:28
LinuxJedicorrect16:28
hallynteward: i'm wondering whehter we can put things in place now to take 1.9 now, and have process ready to take 1.10 as an exceptional sru in 16.0516:28
hallynor, again,16:28
hallynask upstream for a alpha or beta release in feb or march of 201616:29
smoserhallyn is right. this is not significantly different then what we do for openstack.16:29
smoseror at least possibly not much different16:29
rharperif 1.9.x isn't far apart from 1.10.0, why wouldn't 1.9 have the http2 and other features we'd want in the LTS?16:29
LinuxJediit will16:29
hallynnot htat we want it to become the norm :)  but in 2019 we'll likely be wishing we'd done it16:29
hallynrharper: it's just that 1.9 likely won't be supported for 5 years upstream, so a stable would be nicer for 16.0416:30
tewardrharper: provided Debian has it uploaded and available, I'd rather *not* have to do manual source version merges by hand, although I do so for the PPAs already provided under ~nginx on Launchpad16:30
LinuxJedi1.9.x is mainline where new features are added. 1.10.0 will be the end release of the 1.9.x series16:30
rharperright, the support from upstream16:30
rharperteward: and the package maint;16:30
hallynteward: ok, let's see if rbasak is willing to take this to release team, if not i'll volunteer ,t ocome up with options16:31
LinuxJediwe have odd numbers for mainline and even numbers for stable. And only one odd and one even maintained at any time (so currently 1.8 and 1.9 are maintained)16:31
hallynok how long will 1.10 be supported?16:31
LinuxJediuntil 1.1216:31
hallynwhich is when16:31
tewardhallyn: ack16:31
tewardhallyn: april 201716:31
hallynnyears16:31
hallynhm16:31
LinuxJedi1 year16:31
hallynso tha'ts not much of an extra cushion16:31
hallynso we really want an MRE here or something16:32
tewardhallyn: MRE was considered in the past but we have a weird exception:16:32
tewardnginx-core is in main, the other flavors are in Universe, because of third party modules16:32
tewardand security team suggestions/recommendations during the MIR16:32
teward(back for 14.04)16:32
hallynok i'll need to go read the MIR comments then16:32
hallyn(assuming rbasak doesn't handle it :)16:33
tewardhallyn: i think the MRE discussion wasn't on the MIR, and was handled after the fact16:33
hallynteward: do you have links?  can you send them in a reply to sarnold's email?16:33
hallyn(bc i haven't got the thread to reply to)16:33
tewardhallyn: to the discussions?  I could try and find the irclogs links, but I think my discussions with rbasak on that were in private16:33
hallynoh, ok16:33
hallynnp16:33
tewardthe MIR was https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/126271016:34
ubottuUbuntu bug 1262710 in nginx (Ubuntu) "[MIR] nginx" [Undecided,Fix released]16:34
hallynarosales: can you post an action for me to follow up (email rbasak etc)?16:34
arosales#action hallyn to see if rbasak is willing to take this (nginx version in 15.10 and looking to 16.04)  to release team, if not hallyn to volunteer, to come up with options16:34
meetingologyACTION: hallyn to see if rbasak is willing to take this (nginx version in 15.10 and looking to 16.04)  to release team, if not hallyn to volunteer, to come up with options16:34
hallynthx16:34
arosalesthanks hallyn16:34
smoserthank you teward16:34
tewardyou're welcome, and thank you all for your time on this :)16:34
arosalesteward, and LinuxJedi thanks for bringing up this topic16:34
LinuxJedino problem16:35
arosalesany other items to discuss?16:35
tewardarosales: you're welcome, thank you to the Server Team for taking the time to discuss.16:35
arosalesteward, np thats what this meeting is for. Sorry for missing your agenda item :-/16:35
tewardarosales: mistakes happen, no worries :016:35
teward:) *16:35
arosales#topic Announce next meeting date, time and chair16:36
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Announce next meeting date, time and chair
arosales#info chair = hallyn per the list16:36
hallynwoohoo16:36
arosales#info NEXT MEETING: Tuesday 2015-06-23 at 1600 UTC16:36
arosalesthanks everyone16:36
arosales#endmeeting16:36
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Jun 16 16:36:55 2015 UTC.16:36
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-06-16-16.02.moin.txt16:36
tewardthanks, all.16:37
tewardthanks LinuxJedi for taking the time out of your schedule to be here :)16:37
LinuxJedino problem. If you need me for any followups feel free to shoot me a message or email :)16:37
tewardLinuxJedi: will do, thanks again.16:37
tewardand thanks, arosales, and server team.16:37
jsalisbury#startmeeting17: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/Meeting17:00
meetingologyMeeting started Tue Jun 16 17:00:02 2015 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable commands: action commands idea info link nick17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Wily17:00
jsalisbury# Meeting Etiquette17: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
jsalisburyRoll Call for Ubuntu Kernel Weekly Status Meeting17:00
bjfo/17:00
henrixo/17:00
ogasawarao/17:00
argesi/17:00
sforsheeo/17:00
smbo/17:00
ckingo/17:01
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Release Metrics and Incoming Bugs (jsalisbury)
jsalisburyRelease metrics and incoming bug data can be reviewed at the following link:17:01
jsalisbury[LINK] http://kernel.ubuntu.com/reports/kt-meeting.txt17:01
jsalisbury..17:01
jsalisbury[TOPIC] Status: Wily Development Kernel (ogasawara)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Status: Wily Development Kernel (ogasawara)
ogasawaraOur wily kernel remains rebased on 4.0.5.  We have uploaded but are17:01
ogasawaraplanning to land some additional config changes before we have the17:01
ogasawarakernel promoted out of wily-proposed.  Stay tuned.  We have also moved17:01
ogasawarato tracking 4.1-rc8 on our master branch in17:01
ogasawaragit://kernel.ubuntu.com/ubuntu/unstable.git .  We will plan to rebase17:01
ogasawaraWily to 4.1 final once available.17:01
ppisatio/17:01
ogasawara-----17:01
ogasawaraImportant upcoming dates:17:01
ogasawara[LINK] https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule17:01
ogasawaraThurs June 25 - Alpha 1 (~1 week away)17:01
ogasawaraThurs July 30 - Alpha 2 (~6 weeks away)17:01
ogasawara..17:01
jsalisbury[TOPIC] Status: CVE's17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's
jsalisburyThe current CVE status can be reviewed at the following link:17:02
jsalisbury[LINK] http://kernel.ubuntu.com/reports/kernel-cves.html17:02
jsalisbury..17:02
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/Utopic/Vivid (bjf)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Precise/Trusty/Utopic/Vivid (bjf)
bjfStatus for the main kernels, until today:17:02
bjf  * Precise - Prep17:02
bjf  *  Trusty - Prep17:02
bjf  *  Utopic - Prep17:02
bjf  *  Vivid  - Prep17:02
bjf 17:02
bjfCurrent opened tracking bugs details:17:02
bjf  * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html17:02
bjfFor SRUs, SRU report is a good source of information:17:02
bjf  * http://kernel.ubuntu.com/sru/sru-report.html17:02
bjf     17:02
bjf 17:02
bjfSchedule:17:02
bjf 17:02
bjfcycle: 13-Jun through 04-Jul17:02
bjf====================================================================17:02
bjf         12-Jun   Last day for kernel commits for this cycle17:02
bjf14-Jun - 20-Jun   Kernel prep week.17:02
bjf21-Jun - 04-Jul   Bug verification; Regression testing; Release17:02
bjf..17:02
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:03
jsalisbury#endmeeting17:03
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Jun 16 17:03:42 2015 UTC.17:03
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-06-16-17.00.moin.txt17:03
elacheche_aniswxl, ping20:03
lunapersahello wxl20:03
wxlwazzup folks20:04
elacheche_anisgood wxl  u?20:06
elacheche_anisdon't( you have a meeting tonight?20:06
wxlhanging in there20:06
wxlbusy at work20:06
wxlyeah in 2 hrs20:06
wxlloco council20:06
elacheche_anis2 hours!!20:07
elacheche_anisin the Fridge's calander it's for 8pm GMT..20:08
wxlwell maybe i got my thing wrong i don't know20:08
elacheche_anisx) :)20:09
lunapersa:/20:10
elacheche_anis:d20:11
elacheche_anis:D20:11
wxlnot sure why i have it in at 320:12
wxlweird20:12
wxlnope no meeting20:24
wxlyay20:24
wxlback to work :)20:24
lunapersaok wxl :)20:26
elacheche_anislucky wxl :D :p20:40
=== howefield_afk is now known as howefield
=== howefield is now known as howefield_afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!