[00:02] <cjwatson> u-k-i-t: There's nothing in the queue as of now, and I didn't see anything from you.  If it doesn't appear in the archives then you should resend.
[00:05] <u-k-i-t> cjwatson: Thanks for the info. Just resent technical-board@lists.ubuntu.com.
[00:06] <cjwatson> u-k-i-t: Approved
[00:06] <u-k-i-t> Cheers
[12:59] <lool> heya
[13:00] <mandel> lool, hi
[13:00] <lool> stgraber, ogra_, plars: Oy
[13:00] <lool> mandel: hey
[13:00] <mandel> lool, I'm invited, right? :)
[13:00] <plars> hi
[13:01] <lool> mandel: you are  :-)
[13:01] <ogra_> moo
[13:01]  * stgraber waves
[13:02] <lool> ok
[13:02] <lool> so we're missing barry and slangasek who worked late yesterday
[13:02] <lool> GOOD NEWS: system-image with download manager is in!
[13:02] <lool> slangasek and barry tested overnight, I've personally tested this in the morning, and it worked
[13:03] <lool> there are some glitches in the UI now, didrocks broke everything again
[13:03] <lool> barry: hey!
[13:03] <barry> hey!
[13:03] <lool> 15:02 < lool> GOOD NEWS: system-image with download manager is in!
[13:03] <lool> 15:02 < lool> slangasek and barry tested overnight, I've personally tested this in the morning, and it worked
[13:03] <lool> 15:03 < lool> there are some glitches in the UI now, didrocks broke everything again
[13:03] <lool> you dind't miss much
[13:03] <lool> mandel, barry: Thanks for your hard work on thislanding
[13:03] <barry> phew :)
[13:03] <mandel> \o/
[13:03] <lool> now we need to keep an eye on this
[13:03] <didrocks> lool: pfff :p
[13:03] <lool> so didrocks, you have pending changes for progress bar?
[13:04] <lool> barry: didrocks' code doens't seem to get the progress notifications, is that known?
[13:04] <barry> lool: yep.  that'll be one of the critical bugs i'm working on for the next s-i
[13:04] <didrocks> lool: for an intedeterminate state, it's waiting first on getting the current image fixed, but again, it's something that people will not see if the daemon behaves correctly
[13:04] <lool> didrocks updated the code to be async instead of sync when calling into dbus when talking to s-i, which means the button returns immediately which is confusing, but has an update to change this
[13:04] <mandel> and I fixed the 200% issue sin the notifications from the u-d-m and was landed
[13:05] <lool> ok; so next: updated UI code, fixed progress signals, tracking channel aliases, and I'm missing one
[13:06] <lool> manifests
[13:06] <barry> phased updates
[13:06] <lool> and phased udpates, that's hte one I was trying to recall
[13:06] <lool> ok
[13:06] <mandel> lool, I'm concerned about bug #1233435
[13:06] <lool> stgraber: nothing on your side, except we have a major regression in user:group bind-mounts
[13:06] <lool> stgraber: var/lib/usermetrics is root:root in latest image
[13:07] <lool> stgraber: not sure what broke it; the cdimage tarballs are correctly 102:104
[13:07] <mandel> lool, check my last comment in that bug, it seems that we cannot trust the qt libs regarding the state of the network, and that means we might have issues with phones that are performing updates in weak connections
[13:07] <lool> mandel: so that's actually a pretty common use case indeed
[13:08] <mandel> lool, I would expect it to be so
[13:08] <plars> I've had an issue at home for a while, that I haven't seen in the lab, where even though I have wifi set up, sometimes it boots and the default route goes through 3g
[13:08] <plars> maybe related? not sure
[13:08] <mandel> lool, I'm digging to find out what is the exact issues but it seams to be a problem in the QSystenNetworkInfo and QNetworkAccessManager in the images
[13:09] <lool> plars: that's more of an indicator-network / network-manager issue
[13:09] <stgraber> lool: yeah, I'm debugging that right now
[13:09] <lool> mandel: so in any case, there should be definitive timeouts more aggressive than 5 minutes
[13:09] <lool> mandel, barry: Can we make sure at some level that things don't stall for more than 1mn or are retried?
[13:09] <barry> plars: i know slangasek was seeing some weird stuff yesterday related to 3g slowness.  don't know too many details
[13:09] <lool> not from scratch though
[13:10] <lool> mandel: what happens when I'm behind a nocatsplash firewall
[13:10] <mandel> lool, I can try and so something smart
[13:10] <lool> I mean behind a paywall
[13:10] <mandel> lool, hm.. annoying indeed
[13:10] <lool> didrocks: is a cancel download button planned?
[13:11] <didrocks> lool: it's in the UI
[13:11] <didrocks> barry just need to send the progressupdate signal so that it's shown
[13:11] <lool> barry: ok, so given there's a cancel button, perhaps you want to flip back the download on wifi by default bit
[13:11] <didrocks> oh, no, it's a pause
[13:11] <didrocks> if there is something wrong
[13:11] <didrocks> then, there is cancel
[13:11] <didrocks> (like a failure)
[13:11] <lool> barry: but that's low priority anyway
[13:11] <didrocks> but in the spec, it's only pause first
[13:11] <lool> since we're not detecting new OS updates anyway
[13:11] <mandel> lool, I'll take a look at that, but looking at the error with the QNetworkAccessManager::networkAccessible method..
[13:12] <barry> lool: do you mean, download only over wifi?  i think that's the default now
[13:12] <mandel> I'd like to know to who I can bother with this issues, any ideas?
[13:12] <lool> barry, didrocks: Hmm ok, I'm worried that the default user experience might not be what we're looking for, but it's more important that it works solidly
[13:12] <lool> barry: ok
[13:12] <lool> mandel: ok
[13:13] <mandel> barry, lool don't trust that default, I'm not longer trusting QNetworkSystemInfo
[13:13] <mandel> at least until I test it with a nexus 4
[13:13] <lool> mandel: you're no longer trusting Qt it seems  :-)
[13:13]  * barry nods
[13:13] <mandel> lool, some parts of qt :)
[13:13] <lool> hmm I thought i had invited folks for status of upgrade tests
[13:13] <mandel> lool, the ugly ones I'm hiding from other developers
[13:14] <lool> plars: would you be able to cover these?
[13:14] <plars> lool: I don't know anything new on the status of that
[13:14] <lool> plars: ok, what about running tests r/o?  did something change there?
[13:15] <plars> lool: not yet, though the only things we install are the autopilot packages themselves now. I think there were still a few outstanding upstart and/or autopilot issues preventing the click package testing fully
[13:15] <plars> lool: but that's being worked on
[13:15] <lool> ok
[13:16] <plars> lool: hopefully we should have at least some things tested as click packages this week
[13:16] <lool> mandel: so not for 13.10, but I understand we want to do a security review and get QML bindings post-13.10, but nothing else but bug fixes for 13.10; correct?
[13:16] <lool> for now download services is just for system-image, click-scope, click-updater and that's it
[13:17] <mandel> lool, yes, correct
[13:17] <lool> alright, I'm not sure what else we have to cover here
[13:17] <lool> ogra_: anything from you
[13:17] <ogra_> nope
[13:17] <ogra_> trying 5to get us usable images today ... nothing more from me :)
[13:17] <lool> cjwatson: if you happen to be around, would you have an ETA on landing of Ursula's branch to have changelogs of touch images?
[13:18] <cjwatson> lool: No, sorry, I'll see what I can do this week
[13:18] <lool> stgraber, didrocks, barry: I wanted to propose moving right now to URLs for image changelogs from system-image.u.c json's down to UI, and letting the UI display the URL for now, and switch to displaying HTML later
[13:18] <cjwatson> Keeps falling off my list :(
[13:18] <lool> cjwatson: ok, would you think you could tell us the format of URLs in advance?
[13:18] <didrocks> lool: +1
[13:18] <lool> that way we can integrate it through the pipe
[13:18] <cjwatson> lool: Not off the top of my head
[13:19] <barry> lool: i don't think that changes anything in s-i.  we just feed that data through (well, modulo the array-of-dicts qt dbus issue)
[13:19] <lool> cjwatson: Ok; would be nice when you know it to pass it to stgraber so that we start including it in json etc.
[13:19] <lool> stgraber: well, maybe we can provision a fake URL right now
[13:19] <lool> barry: exactly, it avoids the multiple language, large dbus transfer, and the dbus dict issue
[13:20] <barry> lool: so, squash the i18n descriptions?
[13:20] <barry> (that's the only reason why we have to have an array-of-dicts)
[13:20] <cjwatson> It doesn't look like Ursula's branch actually quite finishes hooking it up to publication
[13:20] <lool> stgraber: Hmm why don't we just provision the ~ogra URL for now actually?  that would only show changes from previous image, but that's helpful to test  :-)
[13:20] <barry> and that *would* require changes in s-i
[13:20] <lool> barry: well your insights appreciated on whether we want to do this or not
[13:21] <ogra_> lool, the script runs on my desktop and rsyncs the results ...
[13:21] <ogra_> it might not be reliable (though it was up to now)
[13:21] <lool> ok
[13:21] <lool> not like we'd release with it anyway
[13:21] <ogra_> its fine as interim solution
[13:21] <lool> just trying to show something to users
[13:21] <ogra_> but i wouldnt build services around it
[13:21] <lool> stgraber: your thoughts on URL vs. full description?
[13:21] <stgraber> lool: alright, problem figured out, reading the backlog now :)
[13:22] <barry> lool: i don't think it would be too difficult to change (but probably a bit of fun updating the tests).  it's all a matter of available cycles and priorities.  i guess stgraber and i can discuss spec/server changes
[13:22] <lool> barry: the goal is simplification, if it's a lot of work to change back, then let's not do this
[13:22] <barry> one thought: if we just drop the i18n part of descriptions, it might not be so bad.  i actually don't think we're deploying any i18n descriptions  *anyway*
[13:23] <barry> lool: i'd say if we want to re-enable i18n descriptions later, let's not change it now.  if we're ditching them permanently, then maybe i can squeeze it in
[13:23] <lool> barry: exactly; i18n descriptions wont be there anyway
[13:23] <lool> ok
[13:23] <lool> I think it makes sense to have i18n desc later
[13:23] <lool> in production
[13:23]  * barry nods
[13:24] <barry> i'd rather not churn on this atm
[13:24] <lool> barry: Ok; I'd just want to see some server-side data make it down to the UI, is this hooked up, or should we consider dropping changelogs together?
[13:24] <lool> like, all empty
[13:24] <stgraber> lool: so I think it's a bad idea to require the description field to be a URL because of a limitation in some local libraries, I would rather we stick with what we said back in Oakland, which is that this field is a text field which may contain only a URL in which case the UI is supposed to either link to that or show it in a webkit widget
[13:25] <barry> lool: right now, we don't send the ui *any* descriptions because qt dbus can't handle the data structure.  it's all commented out.
[13:25] <lool> stgraber: sounds good to me
[13:25] <lool> barry: so we're missing serialization of dict to string?
[13:25] <lool> this sounds like json to me
[13:25] <stgraber> lool: also, the path under which the changelogs will appear on cdimage is irrelevant since system-image will have to process those anyway for the diffs, we won't link to cdimage but instead have some /changelogs/... kind of path on system-image (or in the pool)
[13:26] <barry> lool: python can send it; qt apparently can't consume it ;)
[13:26] <didrocks> (can't easily, yeah)
[13:26] <stgraber> barry: so an alternative is to have the UI give you the locale, then you can just return a string
[13:26] <mandel> barry, what data structure?
[13:26] <mandel> barry, I can't believe that...
[13:26] <mandel> 'til I try at least :)
[13:26] <barry> mandel: array of dicts of strings
[13:27] <lool> stgraber: can we start putting some fake server-side data in the images?  like the image number, or just a static string
[13:27] <lool> stgraber: so that we test the full path of descriptions
[13:27] <mandel> barry, aa{ss} ???
[13:27] <barry> mandel: aa{ss}
[13:27] <barry> yep
[13:27] <mandel> barry, let me right an example :)
[13:27] <stgraber> lool: I've been putting something in that field since I first ran the server code ;)
[13:28] <mandel> barry, if I write a sever thar takes it you will take it as it can be done?
[13:28] <lool> I personally think this is a non-problem, we can serialize in JSON between client and UI; it's all in the same image, we can update them together later for something nicer
[13:28] <barry> mandel: that would be great.  please coordinate w/didrocks on that.  for me, it's a simple "uncomment these lines" :)
[13:28] <stgraber> lool: it currently contains the version_detail content
[13:28] <lool> I just want something that takes zero time to write and works  :-)
[13:28] <mandel> didrocks, I'll try to get something for you :)
[13:28] <lool> stgraber: oh cool
[13:28] <stgraber> lool: (and I believe QA currently uses that to figure out what's in the image)
[13:29] <lool> Ok; running out of time
[13:29] <didrocks> mandel: thanks!
[13:29] <didrocks> mandel: basically, all Qt experts in the company told that you need to unmarshmall manually
[13:29] <lool> mandel, barry, didrocks: I'm sure you guys will figure something out; we're running out of time to update system-image and settings though, so let's get this done super soon along the other 13.10 changes   :-)  (no pressure, as usual)
[13:29] <mandel> didrocks, and that is a piece of cake!
[13:29] <lool> ok, any last words?
[13:29] <mandel> didrocks, I'll write the cpp code for you that does it and then copy/paste :)
[13:30] <lool> outside of "arghhh"
[13:30]  * barry was going to use 3g's and 7h's
[13:30] <didrocks> mandel: oh, excellent!
[13:30]  * lool wondered what 3G had to do with this
[13:30] <mandel> why are pirate call pirates? because they arghhh
[13:30] <mandel> sorry I had to say it :)
[13:30] <lool> and 7 hours
[13:30] <didrocks> mandel: sorry, i'm more on the landing side since I'm back, so yeah ;)
[13:30] <lool> alright, thanks all!
[13:30]  * barry says arggghhhhhhh
[13:31] <didrocks> thanks
[13:31] <barry> sorry bad joke
[13:31] <mandel> didrocks, no worries, I'll take care of that
[13:31] <lool> barry: yup, I did get it, but had to reread 3d and 7h multiple times  :-)
[13:31] <barry> :)
[13:31] <lool> bye!
[13:31] <barry> cheers!
[13:32] <mandel> laters o/
[13:32] <mandel> didrocks, I'l ping you asap with an example
[13:32] <didrocks> mandel: excellent!
[16:00] <jamespage> o/
[16:00] <arosales> o/
[16:01] <adam_g> o/
[16:01] <yolanda> hi
[16:01] <yolanda> shall we start?
[16:01] <yolanda> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Oct  1 16:02:14 2013 UTC.  The chair is yolanda. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:02] <yolanda> #topic Review ACTION points from previous meeting
[16:02] <yolanda> smoser look at / assign bug 1206872 and bug 1156932
[16:03] <yolanda> smoser *
[16:03] <yolanda> ^
[16:04] <yolanda> anyone has feedback about that?
[16:05] <jamespage> novaclient won't fix that I suspect
[16:06] <jamespage> yolanda, bug 1206872 is not specifically important for server this cycle
[16:06] <jamespage> so I'd skip that
[16:06] <yolanda> so we postpone that?
[16:07] <yolanda> ok , let's continue
[16:07] <yolanda> #topic Saucy Development
[16:07] <yolanda> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:08] <yolanda> #subtopic Release Bugs
[16:08] <yolanda> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:08] <yolanda> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455
[16:09] <hallyn> smb: ^
[16:10] <yolanda> smb not here, let's continue...
[16:10] <yolanda> https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1213915
[16:11] <jamespage> still with archive-admins
[16:12] <yolanda> https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1199791
[16:12] <jamespage> just pinged one
[16:12] <jamespage> zul, ^^
[16:12] <zul> not done
[16:13] <yolanda> https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1223010
[16:13] <yolanda> zul ^
[16:13] <zul> working on it now
[16:13] <yolanda> https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1231901
[16:15] <yolanda> jamespage ?
[16:15] <jamespage> yolanda, yeah - that popped up last friday
[16:15] <jamespage> rbasak, fyi ^^
[16:15] <jamespage> I'll pick that up this week
[16:15] <rbasak> I hadn't seen that - thanks.
[16:15] <yolanda> ok
[16:15] <jamespage> rbasak, oh - unless you would like to  - feel free
[16:16] <jamespage> it needs a2enmod cgi (which used to happen auto with mpm-prefork)
[16:16] <rbasak> jamespage: I'll put it on my todo and let you know if I get to it first.
[16:16] <yolanda> https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1231970
[16:17] <yolanda> zul ^
[16:18] <zul> watiting for release team
[16:18] <yolanda> ok
[16:18] <yolanda> https://bugs.launchpad.net/ubuntu/+source/python-cliff/+bug/1227167
[16:19] <yolanda> jamespage / smoser ?
[16:19] <zul> that should be fixed already
[16:19] <jamespage> zul, can you check and close the bug if so please
[16:20] <yolanda> zul, i found today that there can be a problem with launchpad branches in python-cliff ?
[16:20] <zul> yolanda: ?
[16:20] <yolanda> ubuntu version was newer than the one downloaded from launchpad
[16:22] <yolanda> zul, python-cliff branch still points to 1.4-1ubuntu1, that is wrong, right?
[16:22] <zul> right
[16:22] <zul> ill have a look
[16:22] <yolanda> cool
[16:22] <yolanda> https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1227353
[16:23] <jamespage> action for roaksoax on that one
[16:23] <jamespage> roaksoax, please add to a suitable seed
[16:23] <jamespage> (do they need to go on the iso per-chance?)
[16:24] <roaksoax> jamespage: im uploading a new maas package today
[16:24] <jamespage> roaksoax, sounds like you are already on top of it  great!
[16:24] <roaksoax> yep!
[16:24] <roaksoax> next upload should contain a fix
[16:24] <yolanda> https://bugs.launchpad.net/uvtool/+bug/1228228
[16:25] <rbasak> This is pending a cloud-init upload I think.
[16:25] <rbasak> smoser?
[16:27] <yolanda> ok, let's continue
[16:27] <yolanda> #subtopic Blueprints
[16:27] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2
[16:29] <yolanda> any updates for it?
[16:29]  * jamespage looks
[16:33] <yolanda> shall i continue?
[16:34] <yolanda> jamespage ^
[16:34] <jamespage> its OK
[16:34] <jamespage> only one todo outstanding
[16:35] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init
[16:36] <yolanda> smoser ^?
[16:36] <jamespage> yolanda, smoser not around right now
[16:36] <yolanda> next one ...
[16:36] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery
[16:37] <jamespage> thats OK
[16:37] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2
[16:37] <jamespage> just waiting on final release
[16:38] <jamespage> roaksoax, ^^
[16:38] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph
[16:39] <yolanda> jamespage ^
[16:40] <jamespage> yolanda, aside from the radosgw geo-replication agents ceph is looking good
[16:40] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa
[16:41] <jamespage> that looks behind
[16:41] <jamespage> I suspect some items to slip to next release - adam_g?
[16:41] <adam_g> ya
[16:41] <adam_g> ill postpone accordingly now
[16:42] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana
[16:43] <jamespage> generally looking OK
[16:43] <yolanda> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb
[16:43] <jamespage> we have one challenge in that OpenStack Havana and Saucy release on the same day
[16:44] <jamespage> so we will zero-day sru havana into saucy
[16:44] <jamespage> mongodb: not so great
[16:44] <jamespage> we won't make the objective to make main this cycle
[16:44] <yolanda> so this will be postponed?
[16:45] <jamespage> yeah - just did
[16:45] <yolanda> ok
[16:45] <yolanda> let's continue
[16:45] <yolanda> #topic Server & Cloud Bugs (caribou)
[16:45] <caribou> Nothing on my radar this week
[16:45] <yolanda> ok
[16:46] <yolanda> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:46] <psivaa> no updates from us :)
[16:46] <yolanda> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:46] <smb> Hi, I have not really made much progress on the nested kvm issue. Did a bit of drbd8 investigation (bug 1185756) and looked into merging back xen-4.3 from Debian to reduce our delta. But I am a bit distracted at the moment by me moving next week. Which will also cause me not to be joining next weeks meeting.
[16:47] <yolanda> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:47] <rbasak> No updates from me. Any questions?
[16:47] <yolanda> #topic Ubuntu Server Team Events
[16:48] <yolanda> anything apart from Cloud Summit and next ODS?
[16:49] <yolanda> #topic Open Discussion
[16:49] <rbasak> o/
[16:49] <rbasak> Need to nominate someone to drive ISO testing for 1) our final Saucy server images 2) subsequent releases. And do we need a process for this? See: http://irclogs.ubuntu.com/2013/09/30/%23ubuntu-release.html "does anyone have an insight on who is doing signoff for the server images?" --rbasak
[16:49] <rbasak> I'd put that in the agenda but I think you missed it.
[16:49] <rbasak> In the past, we end up with a last minute request from the release manager and scramble to find someone to do the ISO testing and put the results in the tracker.
[16:49] <rbasak> It'd be nice to have this planned in advance.
[16:50] <rbasak> jamespage or smoser: any comments?
[16:51] <jamespage> I'll do it
[16:51] <rbasak> Thanks!
[16:51] <yolanda> ok, any more comments?
[16:52] <yolanda> let's finish then...
[16:52] <yolanda> #topic Announce next meeting date and time
[16:52] <yolanda> Next meeting will be on Tue 8th of October
[16:52] <yolanda> chair will be adam_g
[16:52] <yolanda> #endmeeting
[16:52] <meetingology> Meeting ended Tue Oct  1 16:53:07 2013 UTC.
[16:52] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-01-16.02.moin.txt
[16:52] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-01-16.02.html
[16:53] <yolanda> bye!
[16:53] <hallyn> thanks :)
[16:59] <arosales> yolanda, thanks for chairing.
[17:00] <yolanda> np
[17:01] <jsalisbury> #startmeeting
[17:01] <meetingology> Meeting started Tue Oct  1 17:01:39 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:01] <jsalisbury> ##
[17:01] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:01] <jsalisbury> ##
[17:01] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:01] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:01] <jsalisbury> # Meeting Etiquette
[17:01] <jsalisbury> #
[17:01] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:01] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:01] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:01] <sconklin_> o/
[17:01] <cking> \ö
[17:01] <bjf> o/
[17:01] <ppisati> o/
[17:01] <rtg> o/
[17:01] <sforshee> o/
[17:02] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:02] <ppisati> Nothing new to report this week.
[17:02] <ppisati> ..
[17:02] <henrix> 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:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:02] <ogasawara> || apw       || foundations-1305-arm64-bringup     || 2 work items ||
[17:02] <ogasawara> || cking     || foundations-1308-power-measurement || 1 work item  ||
[17:02] <ogasawara> || smb       || servercloud-s-openstack-hypervisor || 1 work item  ||
[17:02] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:03] <ogasawara> The Saucy kernel is currently rebased onto the v3.11.2 upstream stable
[17:03] <ogasawara> kernel.  If any patches need to land in Saucy, they need to be submitted
[17:03] <ogasawara> immediately.  We are currently 2 days away from Ubuntu Kernel Freeze for
[17:03] <ogasawara> Saucy.  Any patches submitted after Kernel Freeze will be subject to our
[17:03] <ogasawara> SRU policy.
[17:03] <ogasawara> -----
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[17:03] <ogasawara> Thurs Oct 03 - Kernel Freeze (~2 days away)
[17:03] <ogasawara> Thurs Oct 10 - Final Freeze (~1 week away)
[17:03] <ogasawara> Thurs Oct 17 - 13.10 Release (~2 weeks away)
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's
[17:03] <jsalisbury> == 2013-10-01 ==
[17:03] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:03] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <jsalisbury> ..
[17:04] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:04] <bjf> Status for the main kernels, until today (Oct. 1):
[17:04] <bjf>   *   Lucid - Prep
[17:04] <bjf>   * Precise - Prep
[17:04] <bjf>   * Quantal - Prep
[17:04] <bjf>   * Raring  - Prep
[17:04] <bjf> Current opened tracking bugs details:
[17:04] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <bjf> For SRUs, SRU report is a good source of information:
[17:04] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury> Thanks everyone
[17:05] <jsalisbury> #endmeeting
[17:05] <meetingology> Meeting ended Tue Oct  1 17:05:19 2013 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-01-17.01.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-10-01-17.01.html
[17:05] <cking> thanks jsalisbury