/srv/irclogs.ubuntu.com/2013/09/03/#ubuntu-meeting.txt

=== emma is now known as em
loolstgraber, barry: Hey13:01
barrylool: hi13:01
loologra_: hallo13:01
ogra_hey ho13:01
* stgraber waves13:02
loolI think we have two things for this week13:02
loolswitch to new numbers + announcement on one side, and blueprint / starting work for stuff we've discussed at vUDS13:03
loolstgraber, barry: So I read stgraber had tested updating to new version numbers13:03
loolI did too13:03
loolI had to manually trigger the update once13:03
loolthen it picked up the update from 17 to 18 in daily-barry13:04
loolbut first, do you folks have other agenda items?  :-)13:04
* ogra_ doesnt 13:04
barrynope13:04
stgrabernope, first thing on my todo is to drop daily-barry, archive daily and daily-proposed, re-import both of them with the new numbering and write+send the announcement13:05
loolsounds great13:05
barryi haven't tried upgrading since friday, but good to hear it worked for lool  and stgraber13:05
stgraberthen start updating the wiki and file bugs for the next bits on my list (channel aliases being pretty high up on it)13:05
barrywhen do you think we can drop support in the client for the old version numbers?13:06
loolbarry: I had to use the cmdline to trigger the update with -b0 though, but I think that was expected?13:06
barrylool: yes, expected13:06
loolbarry: give it 10 days or so?13:06
barrylool: sounds good to me13:06
barry(tbh, it's more tech debt than anything else)13:06
loolok; there's a hangout with QA team later today where we should get latest status on them testing the new images13:07
loolI think that's all13:07
loolasac: what were your questions WRT the switch?13:07
stgraberbarry: well, in theory you can do that tomorrow since we won't be publishing updates with the new format13:07
barrystgraber: ack13:08
loolhmm right, perhaps we want to keep the option of a roll back for a couple of days13:08
loolbut that's it I guess13:08
asaclool: wanted an ETA when you guys feel we are in a state that we should start focussing on the touch_ro dashboard13:08
stgraberyeah, I guess it doesn't hurt to keep it as a rollback option for a few days13:08
loolasac: last week?  :-)13:08
asaclool: so all the technologyu parts have landed etc.?13:08
loolyes13:09
loolwe switch numbering scheme Friday, so we delayed until today to announce13:09
asace.g. we can go into stabilization/testing and later, switch default mode13:09
asacok13:09
asacso what will be announced today?13:09
looltoday we want to announce that the new images are ready for wide consumption13:09
barrylool: doesn't matter really.  i won't even start on that until after the d/l service integration (unless i find it's a blocker, but i doubt it)13:09
loolI don't think we'll have a phablet-flash default, but we should switch the QA tests to use these now13:10
asaclool: whats the diff on the dashboard?13:10
asaclool: can we get the dashboard first into shape?13:10
barryLP: #122023813:10
asachttp://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/13:10
ubottuLaunchpad bug 1220238 in Ubuntu system image "Remove support for old version numbers" [Low,Triaged] https://launchpad.net/bugs/122023813:10
loolasac: apparently QA team was still converting some tests to run on the host as they were too big to apt-get install13:10
asacthose should have more or less the same results13:10
loolasac: but we have a hangout later today with QA team that might be better suited to bring this up13:10
lool(nobody from QA here013:10
asacso right now we cannot promote images to /current13:10
asacwhich means its not very good if we ask folks to move over13:11
asaclets first get our dashboard in shape13:11
loolbarry: might want to check with mandel when the updated download service is landing13:11
loolbarry: he seemed to be changing the API a bit; not much, but still13:11
barrylool: yep, on my plate :)13:11
asaclool: do we have a tool to promote images?13:11
asacis that one ready?13:12
loolasac: it's hooked to the promotion of current13:12
asacok13:12
asacwell not so ok :)13:12
asacbut ok13:12
asac:)13:12
loolwell, you could switch it manually if needed I guess13:12
loolstgraber: ^13:12
asacso lets not announce them until we have valid results13:12
loolbut we should avoid this13:12
loolasac: I'm not in favor of delaying the announcement13:12
loolwe want more people testing these13:12
asaconly if we decouple promotion13:13
asaci dont want to promote stuff like this13:13
asaclool: you can announce that people should try, but dont announce that they should use it as their default13:13
loolso you would like separate promotion of pending -> current and daily-proposed -> daily13:13
loolbecause they are tested separately13:13
asacright13:13
loolI can see how this makes sense, but it's bad if latest daily and latest current are different13:14
asacwe have different results as well13:14
looland we want to stop testing pending -> current altogether13:14
asacnot so sure about that one... for me its two different channels13:14
asacso i dont have a problem if they are out of sync13:14
asacwe want to move over to touch_ro and kill the other13:14
loolyes13:14
asacright. so decouple so we can fix touch_ro13:14
loolso I think it's a bit overzealous to maintain two systems13:14
asacand not stop promoting the old image13:14
ogra_asac, we cant stop promoting it13:15
=== psivaa is now known as psivaa-lunch
ogra_it is used by ports ... we have no option for them to use system image13:15
asacogra_: right. i dont want to stop promoting cdimage-touch13:15
asacwhich would happen if i know that i promoote touch_ro at same time13:15
loolwe will stop testing the cdimage ones13:16
ogra_yeah, we only can do that in case we figure out how community can provide self signed images13:16
loolports can test their own images in situ13:16
asaccan we move that part offline :)13:16
ogra_well, we test the same content in system imagess13:16
asacall i sam saying is: if /pending -> /current automatically promotes touch_ro, then i cant promote cdimage-touch13:16
loolok13:16
ogra_so as long as they work there it is likelz they also work in cdimage images13:16
asacif touch_ro is red13:16
ogra_cdimage touch should jprobably ust drop current and pending ... and grow a /latest :)13:17
loolasac: *we* have a single set of images that we care about; we just keep the option of using cdimage images available for ports, or for engineers that want to test this intermediate step, but it's not considered a product / baseline13:17
asaclets discuss that _after_ we have moved over to touch_ro13:17
asaclool: right, but right now its soo bloody red13:18
loolthe only thing _we_ will be testing are the system-image images13:18
asacif you would have come to me at a day where its 92%13:18
asaci would have had more faith that coupling both is fine for the transition period13:18
ogra_asac, you came to us !13:18
loolasac: but nobody retries stuff on touch_ro13:18
asacbuyt seems that our infrastructure is just not ready for the touch_ro13:18
asacright13:18
asacso lets do that this week13:18
ogra_:)13:18
asacfocus on getting touch_ro also working13:18
asacon infrastructrure13:19
loolstgraber: would you mind attending the QA hangout later today?13:19
asaci would prefer if the system-image team would drive that part13:19
loolI'd like to get a final date agreed to announce this13:19
stgraberlool: sure, I can do that13:19
asace.g. until you reach like 90%13:19
asacthen i am happy to take it over13:19
loolstgraber: I think we should do the renumbering today and announce it though13:19
loolstgraber: perhaps just on ubuntu-phone ML13:19
barry+1 on renumbering announcement13:19
loolasac: who will track the switch of QA to RO images?13:20
loolwe can discuss in the hangout I guess13:20
loolasac: I'll chat with you about this13:20
stgraberyeah, I'll do the renumbering as scheduled13:20
loolok, the other thing is updating the bps post-vUDS13:20
loolstgraber, barry: I didn't copy workitems over from the session13:20
asaclool: this team would drive the part13:21
asacuntil its good13:21
asaclike 80%13:21
asacagain13:21
loolasac: like us?13:21
loolasac: or QA team?13:21
asacno you guys should drive13:21
asacits your landing13:21
asacand you are seeing red in the dashboard13:21
asac:)13:21
loolthis doesn't make sense, we don't have any control over this13:21
asacwell, but you are the drivers13:21
barrylool: i'll double check, though tbh i find the bug tracker a *much* better way to track work than blueprints :/13:21
asacnot saying you have to do all the work13:21
asacjust drive it13:22
loolasac: we can't fix QA infrastructure or QA scripts; we can only advice on how ot implement -- which we did13:22
asaclool: i asked psivaa-lunch now to give it love like we do on touch13:22
asaclool: you can notify them abvout that13:22
asacand ask for retries etc.13:22
asacor ask for help13:22
loolasac: but we want a single contact in QA team; so psivaa you say?13:23
loolok13:23
asaclool: psivaa-lunch and plars are your entry points13:24
asacto get stuff retried13:24
asacetc.13:24
loolstgraber: gah, can't find the bp from 13.08 vuds again13:24
loolah it was upate on OS updates13:24
looland it was just for summit13:24
loolstgraber, barry: Well, bugs are fine for tracking, but to bubble them up to the workitem tracker we need to link them to some blueprint13:25
loolI just wanted us to agree on teh blueprint we'll use going forward13:25
looldo we update the 1305 one, or use the 1308 from vUDS, or yet another one?13:25
stgraberlool: everything on the old one should be marked as done or postponed13:26
stgraberlool: and we should use https://blueprints.launchpad.net/ubuntu/+spec/foundations-1308-os-updates until next vUDS13:26
loolok13:26
barryi'm fine with using the new one.  i'll do some housekeeping on the 1305 one13:27
loolI can copy over stuff from 1305 to 130813:27
loolcan you two update it with new stuff?13:27
barrylool: sure13:27
stgraberyeah, I don't think I've looked at the old blueprint since the last vUDS so I suspect my work items are pretty out of date13:27
barryhttps://blueprints.launchpad.net/ubuntu/+spec/foundations-1305-image-based-updates13:27
loolbarry: just link the bugs there13:27
barrylool: +113:27
loolhmm when using bugs we can't postpone them13:28
loolanyway13:28
loolok; that's all I had13:28
loolanything else from you folks?13:28
barrynope13:28
loolI wanted to make this meeting biweekly with the announcement of new images13:28
loolstgraber, ogra_, barry, asac: Ok; thanks all!13:29
ogra_thanks13:29
stgrabernothing else here. I'll switch to the new version numbers in a bit, it'll take a few hours to re-import everything13:29
barrycheers13:29
stgraberthen will nag QA to re-run the tests and see how things behave. I expect they'll have to go through several run of fixing the tests before things start looking good (I don't expect changes to the image to be required)13:30
stgraberoh and I have no idea how the QA website will handle a new image replacing a broken one in daily-proposed13:30
stgrabersince it'll have the same version number13:31
=== kyleN is now known as kyleN-afk
=== psivaa-lunch is now known as psivaa
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
jamespageo/15:58
jamespageevening folks15:58
smosero/15:59
smb\o15:59
hallyn_\o16:00
adam_go/16:01
zulhiho16:01
hallyn_#startmeeting16:01
meetingologyMeeting started Tue Sep  3 16:02:22 2013 UTC.  The chair is hallyn_. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:01
meetingologyAvailable 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 #votesrequired16:01
hallyn_#topic Review ACTION points from previous meeting16:02
=== meetingology changed the topic of #ubuntu-meeting to: Review ACTION points from previous meeting
hallyn_arosales to update Juju blueprints16:02
arosaleshallyn_, got some good updates during the sprint last week.16:02
hallyn_and bp is updated?16:02
hallyn_will assume yes :)16:03
hallyn_hallyn_ to coordinate with zul and smb on testing xen 4.3 on nova16:03
hallyn_done - tested fine16:03
hallyn_zul to follow up on mariadb/percona making it into Saucy16:03
hallyn_zul: done?16:04
jamespagewe have a catchup in +2 hrs about that with percona16:04
jamespagemariadb is still in review in Debian16:04
hallyn_cool, i'll count that as up-followed16:04
hallyn_thx16:04
jamespageand percona expect to work on it next month16:04
jamespagesaucy looking unlikely16:04
hallyn_ok16:04
hallyn_#topic Saucy Development16:04
=== meetingology changed the topic of #ubuntu-meeting to: Saucy Development
hallyn_#link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server16:05
hallyn_looking through the high prio ones, not sure those pertain to us16:06
hallyn_oh there we go16:06
arosaleshallyn_, yes sorry for the delay. Yes got some good BP updates16:06
hallyn_bug 1208455 - we can talk about during smb's section16:06
ubottubug 1208455 in linux (Ubuntu Saucy) "general protection fault running apt-get inside double nested kvm VM" [High,In progress] https://launchpad.net/bugs/120845516:06
hallyn_arosales: great, thanks16:07
hallyn_bug 121391516:07
ubottubug 1213915 in ceph (Ubuntu Saucy) "Please demote ceph-mds and ceph-fs-common to universe" [High,New] https://launchpad.net/bugs/121391516:07
hallyn_jamespage: ?16:07
jamespagewith archive admins16:07
jamespageno further action on our part required16:07
hallyn_thx16:07
hallyn_bug 120687216:07
ubottubug 1206872 in samba (Ubuntu Saucy) "samba fails to unpack (behavior change in patch) and ftbfs on aarch64" [High,Incomplete] https://launchpad.net/bugs/120687216:07
hallyn_zul: ^ ?16:07
hallyn_also bug 115693216:07
ubottubug 1156932 in python-novaclient (Ubuntu Saucy) "User can't modify security-group-rule via nova-api if there are duplicated security group name" [High,Confirmed] https://launchpad.net/bugs/115693216:08
jamespagethats fixed16:08
zulwill look at it this week16:08
hallyn_and bug 119979116:08
ubottubug 1199791 in nova (Ubuntu Saucy) "nova-compute-xcp misses nova-compute.conf" [High,Triaged] https://launchpad.net/bugs/119979116:08
zuljamespage:  the samba one/16:08
jamespageyeah16:08
jamespagenova security groups thing is not and probably won't be I guess16:08
zuljamespage:  i was hoping for the nova security one ;)16:08
jamespagenah16:08
hallyn_jamespage: sorry, won't be what?16:08
jamespageits not that of a biggy16:08
jamespagewon't be fixed16:08
hallyn_ok16:08
hallyn_last high prio one is bug 121461516:09
ubottubug 1214615 in juju-core (Ubuntu Saucy) "package juju-core 1.13.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2" [High,Fix released] https://launchpad.net/bugs/121461516:09
jamespageI just closed that16:09
jamespageI realized my mistake just after uploading but someone raised a bug Idid not spot16:09
hallyn_i see that :)  thx16:09
hallyn_ok, so moving on to blueprints16:09
jamespagethat horizon r/w on /usr/share is a pig as well16:09
* jamespage bumps the priority16:09
hallyn_jamespage: oh?16:10
jamespageI hit is yesterday when testing a few updates for horizon16:10
hallyn_bug 121601916:10
jamespageI'll have a look16:10
ubottubug 1216019 in horizon (Ubuntu Saucy) "Horizon default config assumes www-data has R/w on /usr/share... directory" [High,Confirmed] https://launchpad.net/bugs/121601916:10
hallyn_jamespage: thx16:10
jamespageyeah - horizon tries to store/retrieve a secret16:10
jamespageis horrid16:10
hallyn_ok, so moving on -16:11
hallyn_[LINK] http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html16:11
hallyn_arosales: jamespage: ^16:11
* hallyn_ defers16:11
jamespagegood oh16:11
arosalessmoser, jamespage did vUDS allow for some good BP updates?16:11
jamespagelooks like everything might have had a good catchup after uds last week16:11
arosalesah ok16:12
jamespageroaksoax, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v216:12
jamespageany updates?16:12
jamespagebah - we are stuck on the hard stuff - active/active rabbitmq and active/active mysql16:12
roaksoaxjamespage: nope, I'll start this week to work on the charms (cause got distracted last week with toher stuff) right now in training16:12
jamespageI started to look at charming percona/cluster using upstream repositories16:13
jamespageit feel fragile still16:13
jamespageanyway..16:13
smoserarosales, i did a far amount of bp updates. if nothing else, vuds did give a reasonable time slot for that.16:13
jamespagesmoser, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams16:13
jamespagehttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init16:13
jamespagehttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa got a bit of a replan post vUDS16:14
jamespageso s'ok16:14
smoserjamespage, simplestreams is in correct state.16:15
jamespagezul, please can you update and re-plan https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana against remaining milestones16:15
smosercloud-init i'm updating now.16:15
zulack16:15
zuljamespage:  will do so this afternoon16:15
jamespageI don't think mongodb will make main this cycle - https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb16:15
jamespagebut hopefully we can figure out something with upstream for 14.0416:16
zularrgh16:16
jamespagethat said we are now ship-shape on OpenSSL + AGPL linking exceptions16:16
* jamespage thanks MongoDB for doing that16:16
jamespagehttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms16:16
jamespageadam_g, I think that needs an update post UDS session please; with milestones etc...16:17
adam_gjamespage, ack16:17
jamespagehttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive16:17
jamespagereplanned and OK16:17
jamespagezul, smb, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor  has some immediate work items that need attention16:18
jamespagespecifcally FFe's for openstack stuff16:18
zulFFE filed for xen16:18
smbhttps://bugs.launchpad.net/ubuntu/+source/xen/+bug/121881716:18
ubottuLaunchpad bug 1218817 in xen (Ubuntu) "[FFE] Update to Xen-4.3 in Saucy" [High,New]16:18
jamespagezul, please update the blueprint then16:18
zulFFE filed for openstack-lxc coming today16:18
jamespagethanks16:18
smbjamespage, thought I did update the bp16:19
jamespagesmb; so you did - my mistake16:19
jamespagearosales, want to touch on the juju blueprints?16:19
jamespageI'm not so close to those...16:19
jamespagenope -OK16:20
jamespagelooks like not to many issues anyway16:20
jamespagehallyn_, back to you16:20
arosalesjamespage, I think we are good for this week16:21
hallyn_jamespage: thanks, moving on,16:21
arosalesplus looks like I lost my chance :-)16:21
jamespagearosales, lol16:21
jamespageblink and you miss it16:21
hallyn_:)16:21
* arosales too slow16:21
hallyn_#topic Ubuntu Server Team Events16:21
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Server Team Events
hallyn_plumber's is comgin up with several mini-confs (lxc, virt, security...)16:21
* smb will be there16:22
hallyn_any more coming up?16:22
arosalescharm school this friday16:22
arosaleshttps://juju.ubuntu.com/events/16:22
arosalesHow to use Charm Helpers16:22
arosales1700 UTC (1pm EDT) 6 September16:22
arosales#juju on Freenode16:22
hallyn_and maybe what charm helpers are? :)  /me should consider listening in16:22
hallyn_ok, moving on,16:22
hallyn_#topic Weekly Updates & Questions for the QA Team (plars)16:22
=== meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions for the QA Team (plars)
arosalesyes if you don't know what charms are please join us and find out :-)16:23
jamespagecharm helpers help you write charms in less code +1000016:23
zullol16:23
hallyn_plars: psivaa: \o16:23
hallyn_we can come back if need be,16:23
hallyn_#topic Weekly Updates & Questions for the Kernel Team (smb)16:23
=== meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions for the Kernel Team (smb)
psivaahello16:24
smbtoo late ? :)16:24
psivaano updaes from us btw :)16:24
hallyn_psivaa: ok thanks :)16:24
smbSo just for that kvm bug mentioned before...16:24
smbI cannot say more than that is seems to be some regression with 3.11 (maybe 3.10 already). I just managed to write a lengthy email to the kvm mailing list this morning as I am not sure how to drill down further. Basing on 64bit Precise  and 64bit Saucy on level 1 for a level 2 should be mostly working but adding more saucy to deeper nesting is likely prone to fail.16:24
hallyn_smb: so 3.9-under-3.9 wouldn't have had this problem?16:24
hallyn_(I thought jodh was having trouble iwth earlier kernels, but maybe i mis-remember)16:25
smbhallyn_, I think only 32bit user-space in level 1 seems to have been broken a bit longer16:25
hallyn_oh. right.  we have multiple bugs?16:25
smbLikely16:25
=== kyleN-afk is now known as kyleN
hallyn_lovely16:25
hallyn_ok so, we're waiting on community to jump in.  this can be rperoduced with fedora or some other distros i assume?16:26
smbI hope but I have not tried16:26
hallyn_ok.  (mahbe i'll try later this week)  any other questions for smb16:26
hallyn_if not, we can move on to...16:27
hallyn_#topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)16:27
=== meetingology changed the topic of #ubuntu-meeting to: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
rbasakNothing new from me. Any questions?16:27
hallyn_(waiting 30 secs for responses)16:27
hallyn_great, let's move on to16:28
hallyn_#topic Open Discussion16:28
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion
hallyn_anything?16:28
rbasakIn case anyone is unaware, http://status.qa.ubuntu.com/reports/ubuntu-server/triage-report.html needs some love.16:28
hallyn_oh yeah - can we do any automated cleanup of the likewise-open bugs?16:29
hallyn_jamespage: ^ that looks like yoru ba16:29
hallyn_bag16:29
jamespagegolly16:30
jamespageyes16:30
jamespageI'll take a look16:30
jamespagebut if the rest of the team can have a dirge on bug triage this week/next that would be helpful16:30
* jamespage holds up his hand for being a little neglegent on triage duty recently16:30
hallyn_jamespage: ok, thanks :)  i looked at some by hand, and actually they looked like not all the same causes - but it's hard to tell bc i don't know the package that well16:30
hallyn_i'd also like to consider taking all < 1000000 numbered likewise-open bugs and marking them all dups or something16:31
hallyn_but ok, let's say16:31
hallyn_[ACTION] everyone spend extra time triaging bugs this week16:31
meetingologyACTION: everyone spend extra time triaging bugs this week16:31
hallyn_so we can move on to16:32
hallyn_#topic Announce next meeting date, time and chair16:32
=== meetingology changed the topic of #ubuntu-meeting to: Announce next meeting date, time and chair
hallyn_Should be Tuesday Sep 10 at 16:00 UTC, with the magnificent roaksoax chairing16:32
hallyn_thanks everyone \o16:32
hallyn_#endmeeting16:32
=== 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 Sep  3 16:33:04 2013 UTC.16:32
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.moin.txt16:32
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.html16:32
jamespagethanks hallyn_16:32
jsalisbury#startmeeting17:00
jsalisbury##17:00
jsalisbury## This is the Ubuntu Kernel Team weekly status meeting.17:00
jsalisbury##17:00
meetingologyMeeting started Tue Sep  3 17:00:36 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable 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 #votesrequired17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:00
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy17: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
ppisatio/17:00
argeso/17:00
ckingo/17:00
henrixo/17:00
apwo/17:00
smb\o17:00
bjfo/17:00
sforsheeo/17:01
ogasawarao/17:01
jsalisbury[TOPIC] ARM Status (ppisati)17:01
=== meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati)
ppisatiLatest bits for Calxeda Midway and LPAE support were pulled in S/master-next.17:01
ppisatiWork continues on making the S/master generic kernel use a concatenated17:01
ppisatiDTB: S/master-next tip has all the necessary config changes, while flash-kernel17:01
ppisatistill needs some work.17:01
ppisati..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://people.canonical.com/~kernel/reports/kt-meeting.txt17:01
jsalisbury..17:01
jsalisbury[TOPIC] Milestone Targeted Work Items (ogasawara)17:01
=== meetingology changed the topic of #ubuntu-meeting to: Milestone Targeted Work Items (ogasawara)
ogasawara[LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork17:01
ogasawara[LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html17:01
ogasawara|| apw       || foundations-1305-arm64-bringup     || 2 work items ||17:01
ogasawara|| ppisati   || foundations-1305-kernel            || 1 work item  ||17:01
ogasawara|| sforshee  || pm-system-policy                   || 1 work item  ||17:01
ogasawara|| smb       || servercloud-s-virtstack            || 1 work item  ||17:01
ogasawara||           || servercloud-s-openstack-hypervisor || 1 work item  ||17:01
ogasawara..17:02
jsalisbury[TOPIC] Status: Saucy Development Kernel (ogasawara)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: Saucy Development Kernel (ogasawara)
ogasawarav3.11 final has been released upstream and we have rebased our Saucy17:02
ogasawaratree.  The archive is however frozen for the Beta-1 release this Thurs.17:02
ogasawaraAs such, Beta-1 will ship with a v3.11-rc7 based kernel.  We will upload17:02
ogasawaraour v3.11 rebased to -proposed and it will propogate to the release once17:02
ogasawarathe archive freeze has lifted.17:02
ogasawara-----17:02
ogasawaraImportant upcoming dates:17:02
ogasawara[LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule17:02
ogasawaraThurs Sep 05 - Beta 1 (~2 days away)17:02
ogasawaraThurs Sep 19 - Final Beta Freeze (~2 weeks away)17:02
ogasawaraThurs Sep 26 - Final Beta (~3 weeks away)17:02
ogasawaraThurs Oct 03 - Kernel Freeze (~4 weeks away)17:02
ogasawara..17:02
jsalisbury[TOPIC] Status: CVE's17:02
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's
jsalisbury== 2013-09-03 ==17:02
jsalisburyThe current CVE status can be reviewed at the following link:17:02
jsalisburyhttp://people.canonical.com/~kernel/cve/pkg/ALL-linux.html17:02
jsalisbury..17:02
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
bjfStatus for the main kernels, until today (Sept. 03):17:03
bjf  *   Lucid - Regression Testing17:03
bjf  * Precise - Regression Testing17:03
bjf  * Quantal - Regression Testing17:03
bjf  * Raring  - Regression Testing17:03
bjfCurrent opened tracking bugs details:17:03
bjf  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html17:03
bjfFor SRUs, SRU report is a good source of information:17:03
bjf  * http://people.canonical.com/~kernel/reports/sru-report.html17:03
bjf..17:03
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:04
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:04
jsalisbury#endmeeting17:04
=== 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 Sep  3 17:05:19 2013 UTC.17:04
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-17.00.moin.txt17:04
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-17.00.html17:04
kamalthanks jsalisbury17:05
=== IdleOne is now known as io
=== freeflying is now known as freeflying_away

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