=== yofel_ is now known as yofel === doko__ is now known as doko === noy_ is now known as noy === cking_ is now known as cking === duanedeisgn is now known as duanedesign === Ursinha-afk is now known as Ursinha === fader_ is now known as fader === UndiFineD is now known as hajour1 === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === hajour1 is now known as UndiFineD === Quintasan_ is now known as Quintasan === jdstrand_ is now known as jdstrand === Ursinha is now known as Ursinha-afk [15:57] * skaet waves [15:57] o/ [15:58] * charlie-tca waves [15:58] hi bjf, charlie-tca [15:58] Good morning, skaet [16:00] looks like its about that time [16:00] not sure if we have quorum or not [16:00] morning all [16:01] morning hggdh :) [16:01] #startmeeting [16:01] Meeting started at 10:01. The chair is skaet. [16:01] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:01] SRU/LTS bi-weekly synch meeting. [16:01] 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. [16:01] morning everyone [16:02] Karmic Koala (9.10) final announce is pending last kernel being published. [16:02] Hardy Heron Desktop (8.04) is waiting for signal as well. [16:02] Dapper Drake (6.06) Server will end of life in June 2011. [16:02] [LINK] https://wiki.ubuntu.com/Releases [16:02] LINK received: https://wiki.ubuntu.com/Releases [16:02] 10.04.3 - July 14-> July 21 - moving it out a week to balance better around Alpha 2. [16:03] .. [16:03] bjf, sconklin when will the last kernel's be ready for publishing for Karmic and Hardy? [16:04] As soon as they are tested and cert and qa and the archive admins sign off. The stable kernel team is finished with them [16:04] sconklin, thanks. [16:05] skaet, as per the email thread on this, this is not the last hardy kernel [16:05] bjf, ok, will go back through my inbox carefully, catching up right now after a week off. [16:06] [TOPIC] Kernel SRU status - sconklin, bjf [16:06] New Topic: Kernel SRU status - sconklin, bjf [16:06] pretty much already been covered. everything is done for the last cycle [16:06] We're about to start another one. [16:07] The dates we're working toward are in the canonical kernel team calendar. When the master calender has dates, we'll work to them [16:08] sorry, ubuntu kernel calendar [16:09] .. [16:09] o/ [16:09] brendand, go ahead [16:10] does this commence the new 3 week cadence? [16:10] yes [16:10] and is the new bug process going to be used? [16:10] "new bug process" == what? [16:10] * JFo is curious [16:11] oh, you mean workflow tools [16:11] yes [16:11] sorry, maybe wrong words. i mean the new SRU workflow [16:11] yes. [16:11] and lastly, where is the ubuntu kernel calendar, for future reference? [16:12] looking for the url [16:12] i'll find it [16:13] sconklin, any concerns about 10.04.3 moving out a week? [16:14] skaet: first I heard about it. Is it in a calendar? probably not a problem but I didn't know we had a master schedule for the next cycle yet [16:15] sconklin, will be getting the master calendar up this week. Just wanted to check with SRU kernel team before putting it up. [16:15] and let others here following this have a chance to flag issues too ;) [16:15] I didn't know where it was scheduled originally even, so don;t know whether a week will make a difference [16:16] https://wiki.ubuntu.com/OneiricReleaseSchedule [16:16] but I doubt it will be a problem [16:16] brendand, skaet, external url for the ubuntu kernel calendar: https://www.google.com/calendar/hosted/canonical.com/embed?src=50d02kfdekgcjdcpc970hh83f0@group.calendar.google.com&ctz=America/Los_Angeles&gsessionid=cp7W8N-DOwo48j_37lbwjg [16:16] thanks bjf [16:16] any other questions for the Kernel team? [16:16] bjf - thanks [16:17] [TOPIC] HW certification - ara [16:17] New Topic: HW certification - ara [16:17] o/ [16:17] brendand will be presenting for the HW certification team from this meeting on [16:17] brendand, ? [16:17] == Hardware Certification SRU Update == [16:17] Certification testing completed for Lucid with 90/105 systems and tracking bug updated. Missing systems are due to lab issues. [16:17] http://people.canonical.com/~hwcert/sru-testing/current/lucid-proposed.html [16:17] Maverick testing in progress. 74/119 systems tested. No regressions found so far. [16:17] http://people.canonical.com/~hwcert/sru-testing/current/maverick-proposed.html [16:17] LINK received: http://people.canonical.com/~hwcert/sru-testing/current/lucid-proposed.html [16:17] LINK received: http://people.canonical.com/~hwcert/sru-testing/current/maverick-proposed.html [16:17] Natty testing in progress. 51/90 systems tested. No regressions found so far. [16:17] http://people.canonical.com/~hwcert/sru-testing/current/natty-proposed.html [16:17] LINK received: http://people.canonical.com/~hwcert/sru-testing/current/natty-proposed.html [16:18] ... [16:18] welcome brendand :) [16:19] what is the outlook on the final testing of Karmic and Hardy kernels? [16:19] skaet - we aren't testing Karmic or Hardy [16:20] brendand, we're at a bit of an impass then. [16:20] o/ [16:20] final kernels have been published, and waiting for cert and qa to weigh in so we can announce EOL. [16:20] bjf go ahead [16:21] o/ [16:21] i think we need someone from the QA team, but I think they were going to test this week [16:21] brad first [16:21] o/ [16:21] :) [16:21] .. [16:21] two things. [16:21] jibel, hggdh, ^^ ?? [16:21] go ahead sconklin [16:21] First, slipping .3 a week actually lines up nicely with our schedule [16:22] second, this is not a final Lucid kernel. We need to stop writing that [16:22] sorry, Hardy [16:22] There is no final desktop kernel [16:23] we continue to produce kernels until server goes out of support [16:23] .. [16:23] sconklin, you had me worried about the lucid ;) noted about hardy- I'll be a bit more careful. [16:23] lucid's time will come ;-) [16:24] ara, go ahead [16:24] thanks [16:24] in the hw cert team we are never testing karmic or hardy. so you guys should only wait on QA for those two [16:25] .. [16:25] hmm... [16:26] I'm going to need to go do some homework then. [16:26] will follow up on email list if warranted. [16:26] anyone around from QA? [16:27] yes [16:27] skaet: ^ [16:27] :) [16:28] we will get it done [16:28] hggdh, cool. you ready to give a status today, or will jibel be doing it? [16:29] skaet: I am not prepared for it, I would rather have jibel doing it (if you do not mind) [16:29] no worries. [16:29] any other questions for brendand ? [16:29] [TOPIC] QA status - jibel [16:29] New Topic: QA status - jibel [16:30] * skaet looks around for jibel? [16:30] [TOPIC] OEM priorities - vanhoof [16:30] New Topic: OEM priorities - vanhoof [16:31] skaet: nothing pressing for the next cycle [16:31] thanks vanhoof. [16:31] is martin s. around? [16:32] ok, [16:32] pitti has a conflict - but no red flags from him. [16:32] support has flagged two bugs to the individual teams [16:33] TOPIC] New business, last chance for general questions? - all [16:33] [TOPIC] New business, etc... [16:33] New Topic: New business, etc... [16:34] skaet: for the record, hardy kernel was approved by QA last week [16:34] thanks hggdh, appreciate the update. :) [16:34] * skaet looks around [16:34] and we will start with Maverick this week (oldest pending kernel) [16:35] * hggdh is done now ;-) [16:35] hggdh, could you look at Karmic so we can formally EOL it? [16:35] skaet: certainly [16:35] thanks! [16:35] #endmeeting [16:35] Meeting finished at 10:35. [16:36] thanks skaet [16:36] thanks sconklin, bjf, ara, brendand, hggdh [16:36] thanks skaet [16:36] thank you, skaet [16:37] skaet: I do not see any karmic kernel in http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html [16:39] hggdh, lets take this up with sconklin and bjf in the #ubuntu-kernel channel. [16:40] skaet: roger wilco [16:40] :) === Ursinha-afk is now known as Ursinha [18:01] o/ [18:02] \o [18:02] shall we get started? [18:03] o/ [18:03] \o [18:03] o/ [18:03] hi everyone! :) [18:03] #startmeeting [18:03] Meeting started at 12:03. The chair is jdstrand. [18:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:03] The meeting agenda can be found at: [18:03] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:03] LINK received: https://wiki.ubuntu.com/SecurityTeam/Meeting [18:03] [TOPIC] Review of any previous action items [18:03] New Topic: Review of any previous action items [18:03] blueprints should be (mostly) together now and our release status page up to date: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Oneiric [18:04] our blueprints for this release of course fell out of our UDS discussions [18:04] oh good, I see the workitem tracker has been reset [18:04] kees: yes! I had a feeling it would happen today :) [18:04] I think kees and I need to still do some light review, but by and large the work items should be all set [18:05] I don't think there is a lot to spec out, beyond dbus/apparmor [18:05] [TOPIC] Weekly stand-up report [18:05] New Topic: Weekly stand-up report [18:05] I'll go first [18:05] I'm in the happy place this week (yea) [18:06] I have a dbus-glib update I am getting back into. some my testing for that will help me define the test cases for the dbus/apparmor bp, which I hope to start looking at again this week. depending on what pops up, it is at least theoretically possible for me to pick up another update [18:07] other than a few administrative things that don't I don't need to waste time here with, I think that is it from me [18:07] kees: you're up [18:07] okay, I'm on triage. I've at least got exim4 to do, and the hardy kernel announcement [18:08] after that, I'm trying to grind out all the graph data work items, since those should fall quickly if I can just get u-c-t to behave. [18:08] \o/ [18:08] I've got some oneiric kernel work to do too (nx-emu rebase) [18:08] * jdstrand hugs kees [18:08] :) [18:08] * kees hugs jdstrand [18:09] I'll probably have some MIR work sprinkled around too. we'll see. :) [18:09] that's it from me. mdeslaur is up. [18:09] mdeslaur: is on holiday today [18:09] s/:/ [18:09] s:// [18:09] hah [18:09] sbeattie: you're up. I can't get my regex right [18:09] dur [18:09] heh [18:10] * sbeattie waits for the regexs to finish. [18:10] s/:// [18:10] :P [18:10] I'm on community this week, after triaging last week. [18:10] I have an apr update in the pipe, though I'm now trying to track down why the lucid arm build failed in a testcase. [18:11] (hooray for the vagaries of chroot builds) [18:12] after that, I want to start poking at my apparmor work items for this cycle. [18:12] I also have some post uds administrivia to complete. [18:12] interesting. I would guess that if it was armel, it wouldn't be chroot specific, but I've not looked at it at all [18:12] (just armel that is) [18:13] * jdstrand also has post uds administrivia [18:13] jdstrand: the testcase that failed had to do with mutexs, so I'm suspecting that its a difference between kernels [18:13] ah [18:13] fun [18:14] yeah. and by yeah, I mean no. [18:14] I think that's it for me. [18:14] hehe [18:14] micahg: you're up! [18:14] so, I have that thunderbird regression with the empty menubar to publish today [18:15] mozilla has announced some of there plans for release schedules [18:15] 3.5 is EOL (doesn't afffect us, just seamonkey will need to go to 2.1.x) [18:15] 3.6 will have updates for the moment [18:15] 4's security update will be 5, so we'll have to upgrade natty on june 21 [18:16] are we still talking about TB? [18:16] nxvl: no, sorry, Firefox [18:16] i assumed :D [18:16] Thunderbird will stay on 3.1.x for the moment [18:16] natty will be our test migration case [18:17] I'll be drafting a page to track what we need to do before the upgrade [18:17] chrisccoulson has done some awesome work to make these transitions smoother WRT language updates [18:18] we'll review at the rally how the natty upgrade went and plan the other migrations (firefox for lucid/maverick and thunderbird in stable) [18:19] so, after drafting the initial plan, I want to try to get the pending webkit updates out [18:20] and I'm expecting a chromium update either this week or early next week [18:20] that's it for me [18:20] micahg: sounds great. thanks! [18:20] [TOPIC] Miscellaneous and Questions [18:20] New Topic: Miscellaneous and Questions [18:22] jjohansen: I'll probably be talking to you later in the week re libapparmor for dbus (all I need is the api call and it to return something based on the env, like we discussed) [18:22] other than that, I don't have anything to add [18:22] jdstrand: okay, sounds good [18:22] does anyone have any other questions or items to discuss? [18:23] going once... [18:24] going twice... [18:24] thanks everyone! :) [18:24] #endmeeting [18:24] Meeting finished at 12:24. [18:24] thanks jdstrand! [18:24] jdstrand: thanks! [18:25] thanks jdstrand [18:25] you bet! :) [20:01] DMB? [20:01] * stgraber waves [20:01] * Laney rings a bell [20:01] * bdrung_ waves. [20:01] hiya [20:02] I was just checking my calendar to make sure I didn't have timezone conversion issue again ;) [20:02] o/ [20:02] google now reminds me via SMS :-) [20:02] persia: maco cody-somerville [20:02] o/ [20:02] hello [20:03] wow, we almost have everyone around this time! [20:03] who wants to chair? [20:04] (we should start deciding at the end of the meeting) [20:04] #startmeeting [20:04] Meeting started at 14:04. The chair is persia. [20:04] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [20:04] [LINK] https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [20:04] LINK received: https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [20:05] [TOPIC] Review progress of probationary period of Marco Rodrigues [20:05] New Topic: Review progress of probationary period of Marco Rodrigues [20:05] cody-somerville, ? [20:05] don't think he is here, and this has been on the agenda for /months/ now [20:05] We should have done it last time: he was there then. [20:06] Right. [20:06] We're waiting for a report. [20:06] [TOPIC] PerPackageUploader Application for John Rigby [20:06] New Topic: PerPackageUploader Application for John Rigby [20:06] [LINK] https://wiki.ubuntu.com/JohnRigby/DeveloperApplication-LinaroLinuxAndUBoot [20:06] LINK received: https://wiki.ubuntu.com/JohnRigby/DeveloperApplication-LinaroLinuxAndUBoot [20:06] jcrigby, How are you today? [20:06] yes for once:) [20:06] On the kmos issue, I think it's a bit unfair to leave it there where people who are interested in the topic never know when it's going to come up. [20:07] I wish you all would pick a meeting when you're going to deal with it and get it over with. [20:07] We should take it to mail and bring it back when it's ready. [20:07] I agree [20:07] Apologies about the kmos situation. +1 for Laney and ScottK's suggestion. [20:07] [AGREED] Remove Review progress of probationary period of Marco Rodrigues from the agenda until there is planned discussion [20:07] AGREED received: Remove Review progress of probationary period of Marco Rodrigues from the agenda until there is planned discussion [20:07] jcrigby, Thanks for coming today. [20:09] glad to be here [20:10] jcrigby, Are you involved in Ubuntu in any way beyond the packages you mention? [20:10] not really no [20:10] hi [20:10] do we have quorum today? [20:10] yes [20:11] yes [20:11] jcrigby, What do you find most difficult about packaging best practices? [20:11] remembering the incantations [20:12] jcrigby: (after persia's question[s]) Can you briefly explain the major freezes in the Ubuntu development cycle and how they affect your packages? [20:12] Laney, I am obviously unprepared for that one [20:12] jcrigby: why do we have special linaro packages in addition to the normal package (e.g. u-boot and u-boot-linaro)? [20:12] Linaro is on its own schedule [20:13] oh, good to know [20:13] bdrung_, actually u-boot-linaro is the only u-boot now days [20:13] ubuntu uses u-boot-linaro [20:13] Are these packages not subject to the Ubuntu release schedule? [20:13] maco: we (Linaro) release ~month after Ubuntu [20:14] Laney, for this oneiric Linaro is releasing monthly [20:14] maco: but recently we switched most of teams to monthly releases [20:14] jcrigby: what does u-boot-linaro contain in comparison to upstream u-boot? [20:14] Laney, and for releases after ff we will release via a ppa to avoid sru issues [20:14] I believe the packages *should* be subject to the release schedule, as there are images that depend upon them shipped as part of the release. [20:15] jcrigby: was that ff = feature freeze or final freeze? [20:15] maco final [20:15] we can do ffe's for feature freeze [20:16] jcrigby, What considerations do you make when requesting an FFe? [20:16] at that point I only allow bug fixes that are must haves for the release [20:17] no new "nice" features [20:17] Do you maintain separate for-ubuntu and linaro-next trees for this? [20:17] * cody-somerville has to jet; will write e-mail to DMB when I get back. [20:17] see you [20:17] persia, I keep -next git trees but those do not have packaging bits in them [20:18] persia, they are for board enablement folks [20:18] That makes sense. [20:19] on the kernel side I actually do keep a work in progress (wip) tree that does have the packaging in it [20:19] that is for people that are willing to build there own packaged kernel [20:19] and I have tried to help people that want to do that but lack the knowledge [20:20] I have also helped the linaro landing teams with their packagig [20:20] since they are usually enablement people not packaging people [20:21] Anyone else with more questions? [20:21] nope [20:21] nope [20:21] nope [20:22] nope [20:22] nope [20:22] [VOTE] Approve John Rigby (jcrigby) for PerPackage Upload rights to u-boot-linaro and linux-linaro-* [20:22] Please vote on: Approve John Rigby (jcrigby) for PerPackage Upload rights to u-boot-linaro and linux-linaro-*. [20:22] Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot [20:22] E.g. /msg MootBot +1 #ubuntu-meeting [20:23] +0 [20:23] Abstention received from Laney. 0 for, 0 against. 1 have abstained. Count is now 0 [20:23] +0 [20:23] Abstention received from stgraber. 0 for, 0 against. 2 have abstained. Count is now 0 [20:25] +1 [20:25] +1 received from geser. 1 for, 0 against. 2 have abstained. Count is now 1 [20:25] +1 given slangasek's testimonial and an understanding of FF, i'm ok with him [20:25] +1 received from maco. 2 for, 0 against. 2 have abstained. Count is now 2 [20:25] +1 [20:25] +1 received from bdrung_. 3 for, 0 against. 2 have abstained. Count is now 3 [20:25] +1 [20:25] +1 received from persia. 4 for, 0 against. 2 have abstained. Count is now 4 [20:25] [ENDVOTE] [20:25] Final result is 4 for, 0 against. 2 abstained. Total: 4 [20:26] jcrigby, Congratulations. [20:26] jcrigby: congrats! [20:26] thanks [20:26] :-) [20:27] [TOPIC] Contributing Developer application for Phillip Susi [20:27] New Topic: Contributing Developer application for Phillip Susi [20:27] [LINK] https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication [20:27] LINK received: https://wiki.ubuntu.com/PhillipSusi/DeveloperApplication [20:27] psusi, Thanks for coming today. [20:29] Or,maybe next time. [20:29] psusi: care to introduce? [20:30] brad figg i guess? [20:31] [TOPIC] PerPackage Uploader application for Brad Figg [20:31] New Topic: PerPackage Uploader application for Brad Figg [20:31] [LINK] https://wiki.ubuntu.com/BradFigg/DeveloperApplication [20:31] LINK received: https://wiki.ubuntu.com/BradFigg/DeveloperApplication [20:31] yay bjf! [20:31] bjf, Thanks for coming today [20:31] np [20:32] Isn't there a kernel package set? [20:32] there's [20:32] You ask for upload rights to the linux-* packages. Do you want that, or did you mean to apply to be part of the kernel uploaders team? [20:32] i think this was clarified on email as "kernel package set" [20:33] I thought so, just wanted to be clear. [20:33] http://paste.ubuntu.com/612008/ [20:33] LINK received: http://paste.ubuntu.com/612008/ [20:33] [LINK] https://launchpad.net/~ubuntu-kernel-uploaders [20:33] LINK received: https://launchpad.net/~ubuntu-kernel-uploaders [20:33] I'm Brad Figg. I've been an Ubuntu contributor since joining Canonical two years ago. I am a member of the Kernel Team. [20:33] I've been a linux developer/user for many years. [20:33] "I was just trying to be clear what I was asking for, if there is a kernel package set then that is what I'm going for." <-- what brad said when Laney asked [20:34] I am currently working on the stable kernel maintenance. I've been doing stable kernel maintenance for two dev cycles and am schedule to continue doing same for another two cycles. [20:34] I'm applying for upload rights for the linux kernel packages. [20:34] I'm proud of the stable work that I've done, we've made some significant changes to the [20:34] stable maintenance process. [20:34] ~ [20:34] i'm good at cut/paste if that is a requirement :-) [20:34] fwiw I've been signing Brad's packages (sponsoring his uploads) for six months, and he's fully capable [20:35] Can you explain how a stable kernel update is typically QAd? [20:36] Also, does the kernel team work with Debian's at all? ;-) [20:36] laney, it's a multi-step process, are you familiar with the kernel cadence that we've gone to? [20:36] somewhat [20:36] * bdrung_ isn't. [20:36] Please share [20:36] laney, yes, we discuss things regularly with the debian kernel folks [20:36] persia, will do :-) [20:37] (especially as ogasawara credits you with bringing order to it) [20:37] https://wiki.ubuntu.com/Kernel/StableReleaseCadence [20:37] currently, we are moving to a three week cadence [20:37] excuse me pasting links [20:37] week 1, we prepare kernels and upload packages (upload to the kernel team ppa) [20:38] week 2, we require verification of LP bugs that have been fixed via the uploaded kernel [20:38] any bugs that fail verification or are not verified, the corresponding commits are reverted and new packages are uploaded [20:38] week 3, the QA and Certification teams take over, and run their tests. [20:39] when does the upload to -proposed happen? what kind of interaction is there with the Ubuntu SRU team? [20:39] bjf: ever had any problems where the reverts after week 2 caused regressions, maybe due to side-effects/interactions between patches & disappearing patches? [20:39] the QA tests are composed of: qbench, tbench tiobench, security tests (crafted by the security team) and some ltp lite tests [20:40] (and regular SRU verification) [20:40] laney, generally we just ping them to pocket-copy, we are changing this as well to use an LP bug for workflow, maybe sconklin can post a url for that as well :-) [20:41] looking [20:41] bjf, pocket-copy to where? [20:41] maco, yes, same proceedure, we revert the commit, roll a new package and upload [20:41] persia, from our ppa to -proposed [20:41] maco, once the new package has been uploaded, qa and cert testing starts again [20:42] maco, this could go on for some time, however, it hasn't in the last two dev cycles [20:42] * Laney is done with questions [20:42] laney, maco, bdrung_ persia the purpose of moving to this cadence is predictability [20:43] bjf: thanks, thats the bit i was unsure about :) [20:43] it was very difficult in the past to be able to give some indication of when a patch was going to get out [20:43] * sconklin is unable to get launchpad qastaging to do anything other than time out [20:43] that's where our example bug is [20:43] as it is now, worst case (baring reversions) is 6 weeks from when a patch is accepted until it hits -updates [20:44]