[13:01] <lool> stgraber, barry: Hey
[13:01] <barry> lool: hi
[13:01] <lool> ogra_: hallo
[13:01] <ogra_> hey ho
[13:02]  * stgraber waves
[13:02] <lool> I think we have two things for this week
[13:03] <lool> switch to new numbers + announcement on one side, and blueprint / starting work for stuff we've discussed at vUDS
[13:03] <lool> stgraber, barry: So I read stgraber had tested updating to new version numbers
[13:03] <lool> I did too
[13:03] <lool> I had to manually trigger the update once
[13:04] <lool> then it picked up the update from 17 to 18 in daily-barry
[13:04] <lool> but first, do you folks have other agenda items?  :-)
[13:04]  * ogra_ doesnt 
[13:04] <barry> nope
[13:05] <stgraber> nope, 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 announcement
[13:05] <lool> sounds great
[13:05] <barry> i haven't tried upgrading since friday, but good to hear it worked for lool  and stgraber
[13:05] <stgraber> then start updating the wiki and file bugs for the next bits on my list (channel aliases being pretty high up on it)
[13:06] <barry> when do you think we can drop support in the client for the old version numbers?
[13:06] <lool> barry: I had to use the cmdline to trigger the update with -b0 though, but I think that was expected?
[13:06] <barry> lool: yes, expected
[13:06] <lool> barry: give it 10 days or so?
[13:06] <barry> lool: sounds good to me
[13:06] <barry> (tbh, it's more tech debt than anything else)
[13:07] <lool> ok; there's a hangout with QA team later today where we should get latest status on them testing the new images
[13:07] <lool> I think that's all
[13:07] <lool> asac: what were your questions WRT the switch?
[13:07] <stgraber> barry: well, in theory you can do that tomorrow since we won't be publishing updates with the new format
[13:08] <barry> stgraber: ack
[13:08] <lool> hmm right, perhaps we want to keep the option of a roll back for a couple of days
[13:08] <lool> but that's it I guess
[13:08] <asac> lool: wanted an ETA when you guys feel we are in a state that we should start focussing on the touch_ro dashboard
[13:08] <stgraber> yeah, I guess it doesn't hurt to keep it as a rollback option for a few days
[13:08] <lool> asac: last week?  :-)
[13:08] <asac> lool: so all the technologyu parts have landed etc.?
[13:09] <lool> yes
[13:09] <lool> we switch numbering scheme Friday, so we delayed until today to announce
[13:09] <asac> e.g. we can go into stabilization/testing and later, switch default mode
[13:09] <asac> ok
[13:09] <asac> so what will be announced today?
[13:09] <lool> today we want to announce that the new images are ready for wide consumption
[13:09] <barry> lool: 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:10] <lool> I don't think we'll have a phablet-flash default, but we should switch the QA tests to use these now
[13:10] <asac> lool: whats the diff on the dashboard?
[13:10] <asac> lool: can we get the dashboard first into shape?
[13:10] <barry> LP: #1220238
[13:10] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/
[13:10] <lool> asac: apparently QA team was still converting some tests to run on the host as they were too big to apt-get install
[13:10] <asac> those should have more or less the same results
[13:10] <lool> asac: but we have a hangout later today with QA team that might be better suited to bring this up
[13:10] <lool> (nobody from QA here0
[13:10] <asac> so right now we cannot promote images to /current
[13:11] <asac> which means its not very good if we ask folks to move over
[13:11] <asac> lets first get our dashboard in shape
[13:11] <lool> barry: might want to check with mandel when the updated download service is landing
[13:11] <lool> barry: he seemed to be changing the API a bit; not much, but still
[13:11] <barry> lool: yep, on my plate :)
[13:11] <asac> lool: do we have a tool to promote images?
[13:12] <asac> is that one ready?
[13:12] <lool> asac: it's hooked to the promotion of current
[13:12] <asac> ok
[13:12] <asac> well not so ok :)
[13:12] <asac> but ok
[13:12] <asac> :)
[13:12] <lool> well, you could switch it manually if needed I guess
[13:12] <lool> stgraber: ^
[13:12] <asac> so lets not announce them until we have valid results
[13:12] <lool> but we should avoid this
[13:12] <lool> asac: I'm not in favor of delaying the announcement
[13:12] <lool> we want more people testing these
[13:13] <asac> only if we decouple promotion
[13:13] <asac> i dont want to promote stuff like this
[13:13] <asac> lool: you can announce that people should try, but dont announce that they should use it as their default
[13:13] <lool> so you would like separate promotion of pending -> current and daily-proposed -> daily
[13:13] <lool> because they are tested separately
[13:13] <asac> right
[13:14] <lool> I can see how this makes sense, but it's bad if latest daily and latest current are different
[13:14] <asac> we have different results as well
[13:14] <lool> and we want to stop testing pending -> current altogether
[13:14] <asac> not so sure about that one... for me its two different channels
[13:14] <asac> so i dont have a problem if they are out of sync
[13:14] <asac> we want to move over to touch_ro and kill the other
[13:14] <lool> yes
[13:14] <asac> right. so decouple so we can fix touch_ro
[13:14] <lool> so I think it's a bit overzealous to maintain two systems
[13:14] <asac> and not stop promoting the old image
[13:15] <ogra_> asac, we cant stop promoting it
[13:15] <ogra_> it is used by ports ... we have no option for them to use system image
[13:15] <asac> ogra_: right. i dont want to stop promoting cdimage-touch
[13:15] <asac> which would happen if i know that i promoote touch_ro at same time
[13:16] <lool> we will stop testing the cdimage ones
[13:16] <ogra_> yeah, we only can do that in case we figure out how community can provide self signed images
[13:16] <lool> ports can test their own images in situ
[13:16] <asac> can we move that part offline :)
[13:16] <ogra_> well, we test the same content in system imagess
[13:16] <asac> all i sam saying is: if /pending -> /current automatically promotes touch_ro, then i cant promote cdimage-touch
[13:16] <lool> ok
[13:16] <ogra_> so as long as they work there it is likelz they also work in cdimage images
[13:16] <asac> if touch_ro is red
[13:17] <ogra_> cdimage touch should jprobably ust drop current and pending ... and grow a /latest :)
[13:17] <lool> asac: *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 / baseline
[13:17] <asac> lets discuss that _after_ we have moved over to touch_ro
[13:18] <asac> lool: right, but right now its soo bloody red
[13:18] <lool> the only thing _we_ will be testing are the system-image images
[13:18] <asac> if you would have come to me at a day where its 92%
[13:18] <asac> i would have had more faith that coupling both is fine for the transition period
[13:18] <ogra_> asac, you came to us !
[13:18] <lool> asac: but nobody retries stuff on touch_ro
[13:18] <asac> buyt seems that our infrastructure is just not ready for the touch_ro
[13:18] <asac> right
[13:18] <asac> so lets do that this week
[13:18] <ogra_> :)
[13:18] <asac> focus on getting touch_ro also working
[13:19] <asac> on infrastructrure
[13:19] <lool> stgraber: would you mind attending the QA hangout later today?
[13:19] <asac> i would prefer if the system-image team would drive that part
[13:19] <lool> I'd like to get a final date agreed to announce this
[13:19] <stgraber> lool: sure, I can do that
[13:19] <asac> e.g. until you reach like 90%
[13:19] <asac> then i am happy to take it over
[13:19] <lool> stgraber: I think we should do the renumbering today and announce it though
[13:19] <lool> stgraber: perhaps just on ubuntu-phone ML
[13:19] <barry> +1 on renumbering announcement
[13:20] <lool> asac: who will track the switch of QA to RO images?
[13:20] <lool> we can discuss in the hangout I guess
[13:20] <lool> asac: I'll chat with you about this
[13:20] <stgraber> yeah, I'll do the renumbering as scheduled
[13:20] <lool> ok, the other thing is updating the bps post-vUDS
[13:20] <lool> stgraber, barry: I didn't copy workitems over from the session
[13:21] <asac> lool: this team would drive the part
[13:21] <asac> until its good
[13:21] <asac> like 80%
[13:21] <asac> again
[13:21] <lool> asac: like us?
[13:21] <lool> asac: or QA team?
[13:21] <asac> no you guys should drive
[13:21] <asac> its your landing
[13:21] <asac> and you are seeing red in the dashboard
[13:21] <asac> :)
[13:21] <lool> this doesn't make sense, we don't have any control over this
[13:21] <asac> well, but you are the drivers
[13:21] <barry> lool: i'll double check, though tbh i find the bug tracker a *much* better way to track work than blueprints :/
[13:21] <asac> not saying you have to do all the work
[13:22] <asac> just drive it
[13:22] <lool> asac: we can't fix QA infrastructure or QA scripts; we can only advice on how ot implement -- which we did
[13:22] <asac> lool: i asked psivaa-lunch now to give it love like we do on touch
[13:22] <asac> lool: you can notify them abvout that
[13:22] <asac> and ask for retries etc.
[13:22] <asac> or ask for help
[13:23] <lool> asac: but we want a single contact in QA team; so psivaa you say?
[13:23] <lool> ok
[13:24] <asac> lool: psivaa-lunch and plars are your entry points
[13:24] <asac> to get stuff retried
[13:24] <asac> etc.
[13:24] <lool> stgraber: gah, can't find the bp from 13.08 vuds again
[13:24] <lool> ah it was upate on OS updates
[13:24] <lool> and it was just for summit
[13:25] <lool> stgraber, barry: Well, bugs are fine for tracking, but to bubble them up to the workitem tracker we need to link them to some blueprint
[13:25] <lool> I just wanted us to agree on teh blueprint we'll use going forward
[13:25] <lool> do we update the 1305 one, or use the 1308 from vUDS, or yet another one?
[13:26] <stgraber> lool: everything on the old one should be marked as done or postponed
[13:26] <stgraber> lool: and we should use https://blueprints.launchpad.net/ubuntu/+spec/foundations-1308-os-updates until next vUDS
[13:26] <lool> ok
[13:27] <barry> i'm fine with using the new one.  i'll do some housekeeping on the 1305 one
[13:27] <lool> I can copy over stuff from 1305 to 1308
[13:27] <lool> can you two update it with new stuff?
[13:27] <barry> lool: sure
[13:27] <stgraber> yeah, 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 date
[13:27] <barry> https://blueprints.launchpad.net/ubuntu/+spec/foundations-1305-image-based-updates
[13:27] <lool> barry: just link the bugs there
[13:27] <barry> lool: +1
[13:28] <lool> hmm when using bugs we can't postpone them
[13:28] <lool> anyway
[13:28] <lool> ok; that's all I had
[13:28] <lool> anything else from you folks?
[13:28] <barry> nope
[13:28] <lool> I wanted to make this meeting biweekly with the announcement of new images
[13:29] <lool> stgraber, ogra_, barry, asac: Ok; thanks all!
[13:29] <ogra_> thanks
[13:29] <stgraber> nothing else here. I'll switch to the new version numbers in a bit, it'll take a few hours to re-import everything
[13:29] <barry> cheers
[13:30] <stgraber> then 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] <stgraber> oh and I have no idea how the QA website will handle a new image replacing a broken one in daily-proposed
[13:31] <stgraber> since it'll have the same version number
[15:58] <jamespage> o/
[15:58] <jamespage> evening folks
[15:59] <smoser> o/
[15:59] <smb> \o
[16:00] <hallyn_> \o
[16:01] <adam_g> o/
[16:01] <zul> hiho
[16:01] <hallyn_> #startmeeting
[16:01] <meetingology> Meeting started Tue Sep  3 16:02:22 2013 UTC.  The chair is hallyn_. 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] <hallyn_> #topic Review ACTION points from previous meeting
[16:02] <hallyn_> arosales to update Juju blueprints
[16:02] <arosales> hallyn_, got some good updates during the sprint last week.
[16:02] <hallyn_> and bp is updated?
[16:03] <hallyn_> will assume yes :)
[16:03] <hallyn_> hallyn_ to coordinate with zul and smb on testing xen 4.3 on nova
[16:03] <hallyn_> done - tested fine
[16:03] <hallyn_> zul to follow up on mariadb/percona making it into Saucy
[16:04] <hallyn_> zul: done?
[16:04] <jamespage> we have a catchup in +2 hrs about that with percona
[16:04] <jamespage> mariadb is still in review in Debian
[16:04] <hallyn_> cool, i'll count that as up-followed
[16:04] <hallyn_> thx
[16:04] <jamespage> and percona expect to work on it next month
[16:04] <jamespage> saucy looking unlikely
[16:04] <hallyn_> ok
[16:04] <hallyn_> #topic Saucy Development
[16:05] <hallyn_> #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:06] <hallyn_> looking through the high prio ones, not sure those pertain to us
[16:06] <hallyn_> oh there we go
[16:06] <arosales> hallyn_, yes sorry for the delay. Yes got some good BP updates
[16:06] <hallyn_> bug 1208455 - we can talk about during smb's section
[16:07] <hallyn_> arosales: great, thanks
[16:07] <hallyn_> bug 1213915
[16:07] <hallyn_> jamespage: ?
[16:07] <jamespage> with archive admins
[16:07] <jamespage> no further action on our part required
[16:07] <hallyn_> thx
[16:07] <hallyn_> bug 1206872
[16:07] <hallyn_> zul: ^ ?
[16:07] <hallyn_> also bug 1156932
[16:08] <jamespage> thats fixed
[16:08] <zul> will look at it this week
[16:08] <hallyn_> and bug 1199791
[16:08] <zul> jamespage:  the samba one/
[16:08] <jamespage> yeah
[16:08] <jamespage> nova security groups thing is not and probably won't be I guess
[16:08] <zul> jamespage:  i was hoping for the nova security one ;)
[16:08] <jamespage> nah
[16:08] <hallyn_> jamespage: sorry, won't be what?
[16:08] <jamespage> its not that of a biggy
[16:08] <jamespage> won't be fixed
[16:08] <hallyn_> ok
[16:09] <hallyn_> last high prio one is bug 1214615
[16:09] <jamespage> I just closed that
[16:09] <jamespage> I realized my mistake just after uploading but someone raised a bug Idid not spot
[16:09] <hallyn_> i see that :)  thx
[16:09] <hallyn_> ok, so moving on to blueprints
[16:09] <jamespage> that horizon r/w on /usr/share is a pig as well
[16:09]  * jamespage bumps the priority
[16:10] <hallyn_> jamespage: oh?
[16:10] <jamespage> I hit is yesterday when testing a few updates for horizon
[16:10] <hallyn_> bug 1216019
[16:10] <jamespage> I'll have a look
[16:10] <hallyn_> jamespage: thx
[16:10] <jamespage> yeah - horizon tries to store/retrieve a secret
[16:10] <jamespage> is horrid
[16:11] <hallyn_> ok, so moving on -
[16:11] <hallyn_> [LINK] http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:11] <hallyn_> arosales: jamespage: ^
[16:11]  * hallyn_ defers
[16:11] <jamespage> good oh
[16:11] <arosales> smoser, jamespage did vUDS allow for some good BP updates?
[16:11] <jamespage> looks like everything might have had a good catchup after uds last week
[16:12] <arosales> ah ok
[16:12] <jamespage> roaksoax, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2
[16:12] <jamespage> any updates?
[16:12] <jamespage> bah - we are stuck on the hard stuff - active/active rabbitmq and active/active mysql
[16:12] <roaksoax> jamespage: nope, I'll start this week to work on the charms (cause got distracted last week with toher stuff) right now in training
[16:13] <jamespage> I started to look at charming percona/cluster using upstream repositories
[16:13] <jamespage> it feel fragile still
[16:13] <jamespage> anyway..
[16:13] <smoser> arosales, i did a far amount of bp updates. if nothing else, vuds did give a reasonable time slot for that.
[16:13] <jamespage> smoser, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams
[16:13] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init
[16:14] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa got a bit of a replan post vUDS
[16:14] <jamespage> so s'ok
[16:15] <smoser> jamespage, simplestreams is in correct state.
[16:15] <jamespage> zul, please can you update and re-plan https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana against remaining milestones
[16:15] <smoser> cloud-init i'm updating now.
[16:15] <zul> ack
[16:15] <zul> jamespage:  will do so this afternoon
[16:15] <jamespage> I don't think mongodb will make main this cycle - https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb
[16:16] <jamespage> but hopefully we can figure out something with upstream for 14.04
[16:16] <zul> arrgh
[16:16] <jamespage> that said we are now ship-shape on OpenSSL + AGPL linking exceptions
[16:16]  * jamespage thanks MongoDB for doing that
[16:16] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms
[16:17] <jamespage> adam_g, I think that needs an update post UDS session please; with milestones etc...
[16:17] <adam_g> jamespage, ack
[16:17] <jamespage> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive
[16:17] <jamespage> replanned and OK
[16:18] <jamespage> zul, smb, https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor  has some immediate work items that need attention
[16:18] <jamespage> specifcally FFe's for openstack stuff
[16:18] <zul> FFE filed for xen
[16:18] <smb> https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1218817
[16:18] <jamespage> zul, please update the blueprint then
[16:18] <zul> FFE filed for openstack-lxc coming today
[16:18] <jamespage> thanks
[16:19] <smb> jamespage, thought I did update the bp
[16:19] <jamespage> smb; so you did - my mistake
[16:19] <jamespage> arosales, want to touch on the juju blueprints?
[16:19] <jamespage> I'm not so close to those...
[16:20] <jamespage> nope -OK
[16:20] <jamespage> looks like not to many issues anyway
[16:20] <jamespage> hallyn_, back to you
[16:21] <arosales> jamespage, I think we are good for this week
[16:21] <hallyn_> jamespage: thanks, moving on,
[16:21] <arosales> plus looks like I lost my chance :-)
[16:21] <jamespage> arosales, lol
[16:21] <jamespage> blink and you miss it
[16:21] <hallyn_> :)
[16:21]  * arosales too slow
[16:21] <hallyn_> #topic Ubuntu Server Team Events
[16:21] <hallyn_> plumber's is comgin up with several mini-confs (lxc, virt, security...)
[16:22]  * smb will be there
[16:22] <hallyn_> any more coming up?
[16:22] <arosales> charm school this friday
[16:22] <arosales> https://juju.ubuntu.com/events/
[16:22] <arosales> How to use Charm Helpers
[16:22] <arosales> 1700 UTC (1pm EDT) 6 September
[16:22] <arosales> #juju on Freenode
[16:22] <hallyn_> and maybe what charm helpers are? :)  /me should consider listening in
[16:22] <hallyn_> ok, moving on,
[16:22] <hallyn_> #topic Weekly Updates & Questions for the QA Team (plars)
[16:23] <arosales> yes if you don't know what charms are please join us and find out :-)
[16:23] <jamespage> charm helpers help you write charms in less code +10000
[16:23] <zul> lol
[16:23] <hallyn_> plars: psivaa: \o
[16:23] <hallyn_> we can come back if need be,
[16:23] <hallyn_> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:24] <psivaa> hello
[16:24] <smb> too late ? :)
[16:24] <psivaa> no updaes from us btw :)
[16:24] <hallyn_> psivaa: ok thanks :)
[16:24] <smb> So just for that kvm bug mentioned before...
[16:24] <smb> I 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:25] <hallyn_> (I thought jodh was having trouble iwth earlier kernels, but maybe i mis-remember)
[16:25] <smb> hallyn_, I think only 32bit user-space in level 1 seems to have been broken a bit longer
[16:25] <hallyn_> oh. right.  we have multiple bugs?
[16:25] <smb> Likely
[16:25] <hallyn_> lovely
[16:26] <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] <smb> I hope but I have not tried
[16:26] <hallyn_> ok.  (mahbe i'll try later this week)  any other questions for smb
[16:27] <hallyn_> if not, we can move on to...
[16:27] <hallyn_> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:27] <rbasak> Nothing new from me. Any questions?
[16:27] <hallyn_> (waiting 30 secs for responses)
[16:28] <hallyn_> great, let's move on to
[16:28] <hallyn_> #topic Open Discussion
[16:28] <hallyn_> anything?
[16:28] <rbasak> In case anyone is unaware, http://status.qa.ubuntu.com/reports/ubuntu-server/triage-report.html needs some love.
[16:29] <hallyn_> oh yeah - can we do any automated cleanup of the likewise-open bugs?
[16:29] <hallyn_> jamespage: ^ that looks like yoru ba
[16:29] <hallyn_> bag
[16:30] <jamespage> golly
[16:30] <jamespage> yes
[16:30] <jamespage> I'll take a look
[16:30] <jamespage> but if the rest of the team can have a dirge on bug triage this week/next that would be helpful
[16:30]  * jamespage holds up his hand for being a little neglegent on triage duty recently
[16: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 well
[16:31] <hallyn_> i'd also like to consider taking all < 1000000 numbered likewise-open bugs and marking them all dups or something
[16:31] <hallyn_> but ok, let's say
[16:31] <hallyn_> [ACTION] everyone spend extra time triaging bugs this week
[16:31] <meetingology> ACTION: everyone spend extra time triaging bugs this week
[16:32] <hallyn_> so we can move on to
[16:32] <hallyn_> #topic Announce next meeting date, time and chair
[16:32] <hallyn_> Should be Tuesday Sep 10 at 16:00 UTC, with the magnificent roaksoax chairing
[16:32] <hallyn_> thanks everyone \o
[16:32] <hallyn_> #endmeeting
[16:32] <meetingology> Meeting ended Tue Sep  3 16:33:04 2013 UTC.
[16:32] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.moin.txt
[16:32] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-16.02.html
[16:32] <jamespage> thanks hallyn_
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Sep  3 17:00:36 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <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:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[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] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <arges> o/
[17:00] <cking> o/
[17:00] <henrix> o/
[17:00] <apw> o/
[17:00] <smb> \o
[17:00] <bjf> o/
[17:01] <sforshee> o/
[17:01] <ogasawara> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> Latest bits for Calxeda Midway and LPAE support were pulled in S/master-next.
[17:01] <ppisati> Work continues on making the S/master generic kernel use a concatenated
[17:01] <ppisati> DTB: S/master-next tip has all the necessary config changes, while flash-kernel
[17:01] <ppisati> still needs some work.
[17:01] <ppisati> ..
[17:01] <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] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17: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:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:02] <ogasawara> v3.11 final has been released upstream and we have rebased our Saucy
[17:02] <ogasawara> tree.  The archive is however frozen for the Beta-1 release this Thurs.
[17:02] <ogasawara> As such, Beta-1 will ship with a v3.11-rc7 based kernel.  We will upload
[17:02] <ogasawara> our v3.11 rebased to -proposed and it will propogate to the release once
[17:02] <ogasawara> the archive freeze has lifted.
[17:02] <ogasawara> -----
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[17:02] <ogasawara> Thurs Sep 05 - Beta 1 (~2 days away)
[17:02] <ogasawara> Thurs Sep 19 - Final Beta Freeze (~2 weeks away)
[17:02] <ogasawara> Thurs Sep 26 - Final Beta (~3 weeks away)
[17:02] <ogasawara> Thurs Oct 03 - Kernel Freeze (~4 weeks away)
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's
[17:02] <jsalisbury> == 2013-09-03 ==
[17:02] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:02] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <jsalisbury> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (Sept. 03):
[17:03] <bjf>   *   Lucid - Regression Testing
[17:03] <bjf>   * Precise - Regression Testing
[17:03] <bjf>   * Quantal - Regression Testing
[17:03] <bjf>   * Raring  - Regression Testing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Sep  3 17:05:19 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-03-17.00.html
[17:05] <kamal> thanks jsalisbury