== Meeting information == * #ubuntu-meeting Meeting, 26 May at 16:00 — 16:12 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-05-26-16.00.log.html]] == Meeting summary == === Review ACTION points from previous meeting === The discussion about "Review ACTION points from previous meeting" started at 16:00. === wily development === The discussion about "wily development" started at 16:01. * ''LINK:'' https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule * ''LINK:'' https://wiki.ubuntu.com/BlueprintSpec * '''Release Bugs''' (16:02) * ''LINK:'' http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server === Server & Cloud Bugs (caribou) === The discussion about "Server & Cloud Bugs (caribou)" started at 16:04. === Weekly Updates & Questions for the QA Team (matsubara) === The discussion about "Weekly Updates & Questions for the QA Team (matsubara)" started at 16:04. === Server & Cloud Bugs (caribou) === The discussion about "Server & Cloud Bugs (caribou)" started at 16:06. === Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges) === The discussion about "Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)" started at 16:07. === Ubuntu Server Team Events === The discussion about "Ubuntu Server Team Events" started at 16:08. === Open Discussion === The discussion about "Open Discussion" started at 16:10. === Announce next meeting date, time and chair === The discussion about "Announce next meeting date, time and chair" started at 16:12. == Vote results == == Done items == * (none) == People present (lines said) == * jamespage (42) * smb (9) * matsubara (4) * meetingology (3) * caribou (3) * arges (2) * rharper (1) == Full Log == 16:00 #startmeeting 16:00 Meeting started Tue May 26 16:00:43 2015 UTC. The chair is jamespage. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:00 16:00 Available commands: action commands idea info link nick 16:00 #topic Review ACTION points from previous meeting 16:00 apparently none so that's good 16:01 #topic wily development 16:01 #link https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule 16:01 o/ 16:01 apparently we're right ontop of feature definition freeze, which means we should all be working to get our blueprints into shape so that we know what 15.10 is going to mean in terms of new stuff 16:02 o/ 16:02 (28th May) 16:02 I'm assuming everyone is familiar with the blueprint template? 16:02 if not 16:02 #link https://wiki.ubuntu.com/BlueprintSpec 16:02 #subtopic Release Bugs 16:02 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html#ubuntu-server 16:03 hmm that appears to be empty 16:03 are we expecting that report to work? 16:03 * jamespage shrugs 16:04 o// 16:04 anyway - not reviewing blueprints today due to point in cycle 16:04 hey arges! 16:04 sorry i'm late 16:04 #topic Server & Cloud Bugs (caribou) 16:04 no caribou today 16:04 #topic Weekly Updates & Questions for the QA Team (matsubara) 16:05 matsubara, you're up :) 16:05 Some trusty smoke tests failed due to a disk space issue in the vm the tests run. It's in my todo list to take a look at that and get them going again 16:05 we'll circle back to caribou 16:05 other than that I have nothing else to report 16:05 jamespage, ^ 16:05 any questions for matsubara ? 16:06 nope ok - thanks matsubara 16:06 caribou, 16:06 #topic Server & Cloud Bugs (caribou) 16:06 sorry for being late; network issues 16:06 nothing particular, aside from some squid-deb-proxy upstart changes that might impact maas 16:07 but kind of OT for this meeting 16:07 fine 16:07 #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges) 16:07 Heya, I have one thing I wanted to mention: 16:07 We have done a lot of hammering bcache with the 3.13 kernel and were 16:07 unable to see any of those lockups/hangs we were hearing about. The 16:07 only guess right now is that those hangs may be related to the use 16:07 of NVMe drives as cache. And even that may require certain revisions 16:07 of the HW / FW. So we cannot support the claim that bcache on a 3.13 16:07 kernel has runtime issues. I anyone thinks there is one, please file 16:07 bug reports with proper detail about used hardware, setup, and usage. 16:07 That be all for today :) 16:07 * jamespage looks sheepish 16:07 thanks smb 16:08 good to know its getting some exercise 16:08 I think we need to circle back to the lab where that issue was seen - later testing was done with HWE kernels 16:08 #topic Ubuntu Server Team Events 16:09 anyone going anywhere good? 16:09 OpenStack summit last week was well attended by Ubuntu folks.... 16:10 #topic Open Discussion 16:10 anyone have anything they want to raise? 16:12 #topic Announce next meeting date, time and chair 16:12 same time next week 16:12 2nd June 1600 UTC 16:12 see you then 16:12 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)