[01:40] <nigelb> 84
[08:03] <weecol> cough cough good morning
[08:04] <weecol> have we a scheduled time for the next meeting
[08:04] <weecol> bots
[08:11] <weecol> botshi
[08:11] <weecol> hi
[08:12] <weecol> do we have work we need discussed?
[08:14] <weecol> i'll idle here then
[12:09]  * Laney phases in
[12:11] <cyphermox> Laney: my application probably can't be processed today seeing as my email made it to devel-permissions. AFAIK it's still held in the moderation queue
[12:12] <Laney> hm, I thought that devel-permissions was unmoderated
[12:12] <Laney> anyway... it appears we are inquorate
[12:13] <RAOF> It is, as long as you've subscribed.
[12:13] <cyphermox> any idea who would be able to release my message?
[12:13] <RAOF> Just Laney and a hopeful RAOF :)
[12:14] <Laney> bdrung is around, but two does not a quorum make
[12:14] <Laney> if more appear later we can maybe have an impromptu session
[12:14] <Laney> sorry all
[12:14] <Laney> cyphermox: I will look into the moderation issue
[12:15] <cyphermox> Laney, thanks
[12:15]  * RAOF slouches off to his UTC+11 bed.
[12:15] <cyphermox> worst case, I can just subscribe and re-send
[12:15] <RAOF> That's what I did :)
[12:16] <cyphermox> ugh, right, this is *really* early for you
[12:16] <cyphermox> or really late ;)
[12:16] <RAOF> Not *desperately* late.
[12:16] <RAOF> 11pm.
[12:16] <RAOF> (11 hours after 12pm ☺)
[12:16] <cyphermox> right
[14:55]  * marjo waves at pitti, ara
[14:56] <pitti> hey marjo, how are you?
[14:56]  * ara waves
[14:56] <marjo> pitti: fine thx; how are you?
[14:58] <zul> hi
[14:59]  * skaet waves
[14:59] <skaet> looks like we're not going to have bjf or sconklin today.
[15:00]  * charlie-tca waves
[15:00] <skaet> do folks want to continue with the meeting,  or shoudl we reschedule?   ara, pitti, marjo?
[15:01] <vanhoof> hi skaet
[15:01] <ara> skaet, I would continue with the meeting, the kernel team can have a look to the meeting logs
[15:01] <marjo> with bjf or sconklin, doesn't make sense
[15:01]  * hggdh waits :-)
[15:01] <marjo> skaet_ ^^^
[15:01] <marjo> but i'll defer to ara :)
[15:01] <ara> but I am easy :)
[15:01] <skaet> hmm,  might be good to get any other issues out,  so,  will go ahead.  :)
[15:02] <skaet> no one will object to a short meeting I suspect?
[15:02] <skaet> :)
[15:02] <skaet> #startmeeting
[15:02] <MootBot> Meeting started at 10:02. The chair is skaet.
[15:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:02] <skaet> Reminder, please follow the convention  of using ".." on a separate line when you've finished typing.    Also, If someone wants to comment on the last point, please "o/", so we know to wait.
[15:02] <skaet> [TOPIC] End of Life - Karmic, Hardy-Desktop
[15:02] <MootBot> New Topic:  End of Life - Karmic, Hardy-Desktop
[15:02] <skaet> ust a reminder that April 2011 will see end of life of Karmic Koala (9.10), and Hardy Heron (8.04) Desktop.
[15:02] <skaet> Dapper Drake (6.06) Server will end of life in June 2011.
[15:02] <skaet> [LINK] https://wiki.ubuntu.com/Releases
[15:02] <MootBot> LINK received:  https://wiki.ubuntu.com/Releases
[15:03] <skaet> ..
[15:03] <skaet> any questions?
[15:04] <skaet> [TOPIC] LTS - 10.04.3
[15:04] <MootBot> New Topic:  LTS - 10.04.3
[15:04] <skaet> milestoned bugs are in the agenda,   10.04.3 is est. July 14th
[15:05] <skaet> please put in agenda if you know of any concerns,  things to avoid around that date.
[15:05] <skaet> milestoned bugs can be found there as well.
[15:05] <skaet> ..
[15:05] <skaet> [TOPIC] Kernel SRU status - skipping this week
[15:05] <MootBot> New Topic:  Kernel SRU status - skipping this week
[15:05] <skaet> [TOPIC] QA status - marjo
[15:05] <MootBot> New Topic:  QA status - marjo
[15:06] <marjo> hi folks
[15:06] <marjo> Lucid
[15:06] <marjo> Testing done on March 9
[15:06] <marjo> https://wiki.ubuntu.com/QATeam/KernelSRU-lucid-2.6.32-30.59
[15:06] <marjo> Lucid EC2
[15:06] <marjo> Testing passed on March 7
[15:06] <marjo> https://wiki.ubuntu.com/QATeam/KernelSRU-lucid-2.6.32-314.27
[15:06] <marjo> Karmic
[15:06] <marjo> Testing done on March 11
[15:06] <marjo> https://wiki.ubuntu.com/QATeam/KernelSRU-karmic-2.6.31-23.74
[15:06] <marjo> Karmic EC2
[15:06] <marjo> https://wiki.ubuntu.com/QATeam
[15:07] <marjo> https://wiki.ubuntu.com/QATeam/KernelSRU-karmic-2.6.31-308.28
[15:07] <marjo> Planned for Week of March 14
[15:07] <marjo> Maverick
[15:07] <marjo> Testing started today March 14
[15:07] <marjo> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/726796
[15:07] <marjo> https://launchpad.net/ubuntu/maverick/+source/linux-backports-modules-2.6.35/2.6.35-28.19
[15:07] <marjo> Hardy
[15:07] <marjo> Testing starts after Maverick tests are completed
[15:07] <marjo> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/725138
[15:07] <marjo> ..
[15:08] <skaet> thanks marjo
[15:08] <marjo> thx skaet
[15:08] <skaet> any questions?
[15:09] <skaet> [TOPIC] HW certification - ara
[15:09] <MootBot> New Topic:  HW certification - ara
[15:09] <ara> o/
[15:09] <ara> This week we reached the coverage of 75 certified systems with 10.04LTS and 75 systems with 10.10.
[15:09] <ara> The tests that failed in Maverick are due to problems with the tests themselves, and are not regressions in the kernel. From our side, Maverick kernel is ready to be uploaded to -updates, as we stated in the tracking bug.
[15:09] <ara> [LINK] http://people.canonical.com/~hwcert/sru-testing/wk10_2011/maverick-proposed.html
[15:09] <MootBot> LINK received:  http://people.canonical.com/~hwcert/sru-testing/wk10_2011/maverick-proposed.html
[15:10] <ara> From the tests that failed in Lucid, we were only suspicious of two failing systems that failed the network tests. That's why we removed the verification-done tag from the tracking bug on Lucid. We just finished investigating those right now and we will now update the tracking bug as we have confirmed that those are not regressions.
[15:10] <ara> [LINK] http://people.canonical.com/~hwcert/sru-testing/wk10_2011/lucid-proposed.html
[15:10] <MootBot> LINK received:  http://people.canonical.com/~hwcert/sru-testing/wk10_2011/lucid-proposed.html
[15:10] <ara> ..
[15:10] <skaet> thanks ara!   what is the root cause of the maverick failures?   some other bugs or hardware?
[15:10] <skaet> sorry
[15:10] <skaet> just re-read what you said
[15:10] <ara> :)
[15:10] <skaet> ok,  test failures.
[15:11] <skaet> anyone else have questions for ara?
[15:11] <skaet> [TOPIC] general SRU status - pitti
[15:11] <MootBot> New Topic:  general SRU status - pitti
[15:11] <pitti> mostly business as usual
[15:12] <pitti> note that this week I'm going to have an SRU training session with SpammapS (Clint Byrum)
[15:12] <pitti> he aggreed to join the SRU team \o/
[15:12] <skaet> *\o/* ;)
[15:12] <pitti> so you might soon see messages and SRU processing from him as well
[15:12] <zul> muhaha
[15:13] <skaet> ..?
[15:13] <zul> never mind me
[15:13] <skaet> nah,  just wondering if pitti was still typing or if he was done?
[15:14] <pitti> ..
[15:14] <skaet> :)
[15:14] <pitti> skaet: (sorry, have the plumber in the flat right now)
[15:14]  * hggdh starts imagining a whole dialog of '..'
[15:14] <ara> hehe
[15:14] <skaet> thanks pitti,  no worries..
[15:14] <skaet> [TOPIC] OEM bug priorities? - vanhoof
[15:14] <MootBot> New Topic:  OEM bug priorities? - vanhoof
[15:15] <vanhoof> skaet: o/
[15:15] <skaet> :)
[15:16] <vanhoof> skaet: we have an on-going issue we're debugging, which may result in a request for SRU, but we're still not close to the final root cause
[15:16] <vanhoof> that's the only pressing item I have open now
[15:16] <vanhoof> everything else is already verified in -proposed, or ack'd appropriately for the next SRU cycle
[15:16] <skaet> ..?
[15:16] <vanhoof> ..
[15:16] <skaet> cool
[15:16] <skaet> thanks vanhoof!
[15:16] <skaet> any questions?
[15:17] <skaet> [TOPIC] Support team - customer bug priorities - martins
[15:17] <MootBot> New Topic:  Support team - customer bug priorities - martins
[15:17]  * skaet looks around though and doesn't see martins,  so we'll come back to this next time....
[15:18] <skaet> [TOPIC] New business, last chance for general questions? - all
[15:18] <MootBot> New Topic:  New business, last chance for general questions? - all
[15:18] <zul> hi
[15:18] <zul> i have one thing
[15:18] <skaet> go zul :)
[15:18] <zul> we have a SRU for bind for a new upstream version (9.7.0 -> 9.7.3)
[15:18] <zul> its at the techboard level https://lists.ubuntu.com/archives/technical-board/2011-February/000709.html
[15:19] <zul> but it hasnt been looked at by the tb yet
[15:19] <zul> and we have a couple of weeks before all hell breaks loose
[15:19] <zul> Daviey is handing it right now
[15:19] <zul> ...
[15:19] <skaet> Thanks for the head's up zul.   what's the bug number?
[15:20] <zul> 651875 i think
[15:20] <zul> mdz just responded to it so its in the SRU team hands now
[15:21] <skaet> pitti, ^^   will get with you about it then offline.
[15:22] <zul> cool thanks!
[15:22] <skaet> zul,  I'll keep it on the "keep close eye on it" then list,  till we know its in the flow, and add it to the agenda to track next meeting.
[15:22] <Daviey> mdz, Thanks for updating that
[15:22] <mdz> Daviey, np, sorry it took so long
[15:23] <skaet> [ACTION] skaet work with zul, Daviey, pitti on 651875 update plans
[15:23] <MootBot> ACTION received:  skaet work with zul, Daviey, pitti on 651875 update plans
[15:23] <skaet> anyone else have questions? new business?
[15:24] <pitti> skaet, zul: that by and large just needs an upload
[15:24] <skaet> :)
[15:24] <skaet> cool
[15:24] <zul> pitti: right ill poke daviey to do it then
[15:24] <skaet> Reminder: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-03-14-SR is where the agenda is being tracked.
[15:25] <skaet> its hot linked from StableReleaseAgenda each meeting.
[15:25] <skaet> let me know off line if you want some items rearranged.
[15:26] <skaet> thanks ara, marjo, pitti, vanhoof, zul, Daviey
[15:26] <skaet> #endmeeting.
[15:26] <marjo> skaet: thx
[15:26] <ara> thanks all!
[15:27] <skaet> #endmeeting
[15:27] <MootBot> Meeting finished at 10:27.
[15:27] <pitti> thanks everyone
[15:27]  * skaet makes note not to put . after endmeeting in future.  :P
[17:04] <jdstrand> kees, sbeattie, micahg, jjohansen: meeting?
[17:04] <jjohansen> \o
[17:04] <kees> o/
[17:05] <micahg> o/
[17:07] <jdstrand> ok, let's start
[17:07] <jdstrand> #startmeeting
[17:07] <MootBot> Meeting started at 12:07. The chair is jdstrand.
[17:07] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:07] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[17:07] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[17:08] <jdstrand> since the security team is in north america, we decided to move the meeting to 1700UTC due to recent DST
[17:08] <jdstrand> (it is a more convient time for members of the team)
[17:08]  * sbeattie is here
[17:08] <jdstrand> [TOPIC] Review of any previous action items
[17:08] <MootBot> New Topic:  Review of any previous action items
[17:09] <jdstrand> I don't see any new action items from last week. so let's move on
[17:09] <jdstrand> [TOPIC] Weekly stand-up report
[17:09] <MootBot> New Topic:  Weekly stand-up report
[17:09] <jdstrand> I'll go first
[17:09] <jdstrand> I am on community
[17:10] <jdstrand> last week was a short week for me, and due to several meetings, patch piloting, training and other surprises, I did very little of what I thought I was going to do last week
[17:10] <jdstrand> we'll see how this week goes :)
[17:10] <jdstrand> currently I have:
[17:11] <jdstrand> USN publication site updates. the ISD team will be making the usn area a 'microsite', and it won't be drupal based
[17:11] <jdstrand> (aiui)
[17:11] <jdstrand> while they are implementing it, I said I would help with direction, feedback and testing
[17:11] <jdstrand> I'd like to get to my QRT fixes/additions to libvirt and apparmor
[17:12] <jdstrand> last week I started on a 'test-net' test for apparmor in QRT, but I didn't finish
[17:12] <kees> For the usb microsite, it would be great if it just read directly from the usn pickle
[17:12] <jdstrand> kees: yeah, I got your email and plan to bring that up with them. that is a good idea
[17:12] <jdstrand> (sorry for not responding to the email)
[17:12] <kees> no worries, figured this was good place to bring it up :)
[17:13] <jdstrand> lots of little bugs/sponsoring accumulating (ufw, libvirt, *blacklists, etc, etc)
[17:13]  * micahg would suggest a cache time of 1hr on the generated pages
[17:13] <jdstrand> I have a lot of piddly stuff I'd just like to sweep away
[17:13] <jdstrand> micahg: noted
[17:14] <jdstrand> assuming I can get through that, I have a dbus-glib update I almost completely forgot about, and would like to see if I can pick anything else up
[17:14] <jdstrand> kees: you're up
[17:14] <kees> okay, I've got a few upstream kernel leaks I'm still trying to get traction on. like everything there, the only way to get some of this stuff fixed is to fix it myself. :(
[17:15] <kees> there was a regression in the tiff update that I'll take
[17:15] <kees> bug 731540
[17:15] <kees> and then I'll just be working through my todo list
[17:16] <kees> graph updates, etc
[17:16] <kees> one things Ng asked about was if we could order CVEs in the USN by priority instead of my serial number.
[17:16] <kees> I'm of two minds about it, but said I'd bring it up
[17:17] <Ng> it was just so that I'd be able to triage USNs and see the scariest things first
[17:17] <jdstrand> most of the USNs that shouldn't be a big deal
[17:17] <jdstrand> the kernel, firefox, webkit, etc can have a few at a time though
[17:18] <sbeattie> openjdk
[17:18] <jdstrand> the kernel is hopefully going to be resolving itself as the backlog is diminishing
[17:18] <jdstrand> sbeattie: true
[17:18] <sbeattie> and a lot of those, we're somewhat swag'ing on the priority level as it is.
[17:18] <jdstrand> hmm
[17:19] <jdstrand> kees: iirc, the tools will sort them no matter what order we enter them. is that right?
[17:19] <kees> the bulk of stuff is medium and its priority to the user depends on their environment
[17:19]  * jdstrand nods
[17:19] <jdstrand> I'm betting Ng is thinking most about kernels
[17:19]  * sbeattie agrees, our medium covers kind of a wide spectrum.
[17:19] <kees> jdstrand: the tools try to produce an ordered list, yes
[17:19] <jdstrand> (of the ones we just mentioned)
[17:20] <kees> what shows up in the USN description, however, can be sorted differently
[17:20] <Ng> jdstrand: yep
[17:20] <jdstrand> kees: true. we could just take it as a TODO and a wiki edit to trye to organize them in the USN by priority, at least for the kernel
[17:21] <kees> I think putting high and critical at the top would be fine. the rest aren't worth ordering, I think.
[17:21] <jdstrand> tbh, I like how the top of the USN has them sorted. I think it makes it easier to see if a particular USN fixes a CVE you are interested in
[17:21] <jdstrand> kees: I agree
[17:21] <kees> right, in the CVE list, I would want it sorted serially
[17:21]  * jdstrand nods
[17:22] <kees> I'll play with having it produce the description list in priority-sorted then serial-sorted order
[17:22] <jdstrand> Ng: if we put high and critical as the first USNs in the description, would that be helpful enough?
[17:22] <jdstrand> err
[17:22] <jdstrand> the first CVEs* in the USN description
[17:23] <Ng> jdstrand: I can't speak for everyone, but I tend to go with the descriptions in the "Details follow" section rather than pull up the full CVE for everything. If you guys say it's a crash only and there's no code execution or privilege escalation I'm unlikely to read the full CVE
[17:25] <Ng> (particularly when a kernel USN references 46 CVE numbers ;)
[17:25] <kees> yeah
[17:25] <kees> okay, i'll give it a shot. that's it from me.
[17:25] <jdstrand> Ng: right. the 'Details follow' is the part I was saying we could put the High and Critical. I think that is a reasonable and doable request (esp wrt the kernel). what do others think?
[17:25] <jdstrand> ok then :)
[17:25] <jdstrand> kees: can you add a small wiki edit too?
[17:25] <jdstrand> sbeattie: you're up
[17:25] <kees> jdstrand: sure
[17:26] <Ng> jdstrand: that would be perfect for me :)
[17:27] <sbeattie> with mdeslaur on vacation for most of this week, I'm covering triage for him.
[17:27] <sbeattie> openjdk-6 arm packages finally built, so I'll be releasing those soon.
[17:28] <jdstrand> sbeattie: thanks for doing triage btw
[17:28] <sbeattie> I have another embargoed issue I'm working on.
[17:29] <sbeattie> And I have a bit of apparmor bugwork and documentation to do.
[17:29] <sbeattie> I think that's it for me.
[17:30] <jdstrand> thanks
[17:30] <jdstrand> micahg: you're up
[17:30] <micahg> There was a chromium chemspill release from pwn2own, so I'm finishing up testing on that
[17:31] <micahg> This week I hope to at least get the webkit update staged
[17:31] <micahg> I also hope to do some triage WRT the webkit CVEs
[17:31] <micahg> that's it
[17:31] <jdstrand> cool
[17:32] <jdstrand> I have to small items
[17:32] <jdstrand> oh
[17:32] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:32] <MootBot> New Topic:  Miscellaneous and Questions
[17:32] <jdstrand> ok, I have 2 small items
[17:33] <jdstrand> watching the vsec demise conversation on oss-security, I noticed that xorg said that distros subscribe to xorg-security@lists.x.org
[17:33] <jdstrand> I am not subscribed to that list personally
[17:33]  * sbeattie either.
[17:33] <jdstrand> we should consider subscribing an individual or the team
[17:34] <jjohansen> team if they will let you
[17:34] <micahg> +2
[17:34] <micahg> oops
[17:34] <micahg> +1
[17:34] <kees> +3 :)
[17:34]  * jdstrand nods
[17:34] <jdstrand> +4
[17:34] <jdstrand> ok, we can look at that
[17:35] <sbeattie> are there other security lists we should have a representative on?
[17:35] <jdstrand> the other thing is that everone should have gotten their performance review email. nothing to discuss there, just be aware of it and if you have questions, ask
[17:36] <jdstrand> sbeattie: probably. though otoh I don't know of any
[17:36] <jdstrand> that is all I have
[17:37] <jdstrand> does anyone have any other questions or items to discuss?
[17:37] <kees> I already did mine (usn cve priority ordering)
[17:38]  * jdstrand nods
[17:38] <jdstrand> alrighty
[17:38] <jdstrand> well, thanks everyone! have a great week :)
[17:38] <jdstrand> #endmeeting
[17:38] <MootBot> Meeting finished at 12:38.
[17:38] <kees> cool, thanks jdstrand !
[17:39] <sbeattie> jdstrand: thanks!
[17:40] <jdstrand> sure thing :)
[17:41] <micahg> jdstrand: tahnks