[05:58] sb levelclear -level clientcrap,crap,joins,parts,quits,nicks,clientnotice [06:02] hyperair: did you forget a / ;) [08:34] nigelb: yeah i did =(( [08:34] nigelb: i did /foreach window, so every channel got it >_< === rpinson_ is now known as raphink === ogra_ac is now known as ogra_ === thermi is now known as Thermi === Ursinha-afk is now known as Ursinha === fader_ is now known as fader === Thermi is now known as thermi === doko_ is now known as doko [15:31] reminder SRU/LTS meeting will start in 1/2 hour. === Thermi is now known as thermi === thermi is now known as Thermi [15:56] * marjo waves to skaet [15:57] hi pedro_ [15:57] hola hola [15:58] oi oi [15:59] \o/ [16:00] hi all [16:00] #startmeeting [16:00] Meeting started at 10:00. The chair is skaet. [16:00] 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] . [16:01] [TOPIC] End of Life - Karmic, Hardy-Desktop [16:01] Just a reminder that April 2011 will see end of life of Karmic Koala (9.10), and Hardy Heron (8.04) Desktop. [16:01] Note will be going out this week, for the one month warning. [16:01] . [16:01] Dapper Drake (6.06) Server will end of life in June 2011. [16:01] New Topic: End of Life - Karmic, Hardy-Desktop [16:01] [LINK] https://wiki.ubuntu.com/Releases [16:01] LINK received: https://wiki.ubuntu.com/Releases [16:01] . [16:01] Any concerns or issues to flag with the approaching EOL? [16:01] .. [16:02] [TOPIC] Kernel SRU status - sconklin, bjf [16:02] New Topic: Kernel SRU status - sconklin, bjf [16:02] In order to sync the kernel cadence schedule back up [16:02] with the master interlock schedule, I've proposed [16:02] that we take the kernels which have been in [16:02] | [16:02] The end result of this is that any changes to kernels which were [16:02] approved after week before last will not show up in -proposed until April 29th [16:02] .. [16:02] did that all make it? [16:02] no [16:02] no :( [16:02] sconklin: no [16:03] ok, here goes again [16:03] In order to sync the kernel cadence schedule back up [16:03] with the master interlock schedule, I've proposed [16:03] that we take the kernels which have been in [16:03] -proposed for a week and just treat them as [16:03] if they were uploaded last Friday. [16:03] | [16:03] This is effectively just putting the kernel cadence on hold for a week. [16:03] | [16:03] The end result of this is that any changes to kernels which were [16:03] approved after week before last will not show up in -proposed until April 29th [16:03] (five weeks from now), and will not be released until May 19th (almost [16:03] eight weeks from now). [16:03] .. [16:03] o/ [16:04] go ara [16:04] I agree with the resync [16:04] but I would like to keep the Maverick cadence if possible [16:05] there are a lot of fixes the the HWE team needs to release [16:05] and 8 weeks is too long time for them to wait [16:06] so my proposal would be [16:06] o/ [16:06] * Resync with QA schedule. This is, keeping this kernel two more weeks [16:06] in -proposed, so QA can test it next week. [16:06] * Keep the cadence for Maverick (uploading new ones April 8th, April 22nd) [16:06] * Start again with the 2 week cadence after UDS (uploading kernels for [16:06] all the releases on May 20th) [16:06] .. [16:06] sconklin go [16:07] ara: that would work well for QA, allows us to concentrate on beta-1 this week [16:08] marjo, what would be one with the April 8th kernels? does the QA team have bandwidth to test them along with the final Natty testing? [16:08] ara, that's fine with the stable kernel team. I think we can meet that, and it would serve some needs that are pretty critical. In general if we're going to split out some series for a different schedule, I;d like to have a good display of what those schedules are, but that's a different problem [16:08] o/ [16:09] bjf, let ara respond and then you go. [16:09] skaet, kernels for April 8th and 22nd would only be for Maverick [16:10] skaet, so, if QA could test those, that would help a lot the HWE team [16:10] .. (forgot) [16:10] .. [16:10] does that mean the current cycle started last Thursday ? it's kind of confusing to start cycles mid week. [16:10] .. [16:11] skaet, ara: the problem w/ kernels for April 8 is conflict w/ testing for beta-2 week of April 11 [16:11] ara, yes, April 22 should probably work out ok (QA testing first week of May), but I'm a bit concerned about April 8th proposal. [16:11] heh [16:11] marjo, I understand, but if they uploda the kernel on Friday, you guys have Friday, Monday and Tuesday for Maverick kernel [16:12] and week of april 25 is final release testing [16:12] marjo, it is very unlikely that the Beta testing start before Tuesday [16:12] ara: sure, very risky imho [16:12] ara, uploaded kernels are tested by week after by QA (validation week first) [16:13] * JackyAlcine will be right back. [16:13] skaet, sorry? [16:13] s/validation/verification [16:13] * skaet sorry [16:14] skaet, then it is perfect, it is the week in between :) [16:14] ara, not quite, we've got holidays that week, and last updates. [16:15] skaet, but, why don't we try? [16:15] skaet, the only thing that can go wrong is that finally we don't have time for the SRU, and it does not get uploaded (as per the kernel team policy) [16:15] ara, +1 [16:16] ara, I'm just worrying about the QA team's bandwidth. [16:16] for the month of april. [16:16] skaet: thx; see above comments [16:16] we'll be doing one cycle already this month, and then one in early may. [16:17] what is the pressure for the fixes to motivate the risk to Natty? [16:17] ara, vanhoof, ^^ ? [16:17] skaet: i have the same question; posed to vanhoof [16:19] o/ [16:19] (when this topic has closed) [16:19] .. [16:19] ,, [16:20] .. [16:20] .. [16:20] * skaet looking around for comments from vanhoof? [16:21] skaet, I think vanhoof is on swap day today [16:21] :( [16:21] ahh, ok, we'll stop waiting then. [16:21] sconklin go, while I try to summarize where we are with the interlock. [16:22] Brad's question went unanswered - Why do schedules start mid-week? It would work much better for us if uploads to -proposed were on Monday and not Friday [16:22] I meant Thursday === bjf is now known as bjf[afk] [16:23] Monday not Thursday [16:23] sconklin, pattern was followed for interlock with development release schedules [16:23] however, the reason for indicating the -proposed (date) [16:24] was to clarify when things were available [16:24] similarily with -update(date) which doesn't happen on thursdayse either. [16:24] interlock, is because testing happens with other teams work on that schedule. [16:24] we can certainly revisit this, and resetting expectations at UDS. [16:25] key is that we have to look at it from the overall viewpoint to keep things sane for the teams that have to work between stable, and development. [16:25] ok, not trying to change anything today but let's open a discussion among the teams about it [16:25] .. [16:26] ok. [16:26] moving on then since I was busy typing ;) will summarize at the end. [16:26] [TOPIC] QA status - marjo [16:26] New Topic: QA status - marjo [16:26] hi folks [16:27] Dapper completed on March 21. No regressions. https://wiki.ubuntu.com/QATeam/KernelSRU-dapper-2.6.15-57.94 [16:27] Hardy completed on March 25. No regressions. https://wiki.ubuntu.com/QATeam/KernelSRU-hardy-2.6.24-29.88 [16:27] New LUB, LBM and LRM installed correctly too. [16:27] skaet: given the previous discussion, are you still interested in possible test plans for this week, or not? [16:28] marjo, am interested in test plans for next week. [16:28] it's getting late on a monday... [16:28] ah ok [16:28] * skaet notes the kernel available should be in verification this week, testing next [16:29] so, next week (week of April 4), the QA team is available for testing Lucid and/or Maverick kernels [16:29] .. [16:30] thanks marjo. [16:31] any question? [16:31] [TOPIC] HW certification - ara [16:31] New Topic: HW certification - ara [16:31] We are waiting for the verification phase to finish to start testing [16:31] sconklin, when are you guys expecting the patches to be verified? [16:31] how is the verification going? [16:31] .. [16:31] one sec [16:33] it looks like we have a couple of bugs left to be verified for lucid and maverick, but if we're resetting the schedule so that verification effectively started Friday, then we should be able to easily get those [16:33] I expect in the next day or so if I start harassing people [16:33] .. [16:33] sconklin, sounds good, let us know when that happens, please [16:33] .. [16:33] http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html [16:33] LINK received: http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html [16:33] latest status is always here [16:33] .. [16:34] sconklin, let me summarize to make sure I'm understanding... [16:35] you'll fiinish off the verifications in next day or two, and then send email to the list. [16:35] at that time QA and HW cert (as their other schedules permit) can start. [16:35] with starting no later than this Friday. [16:36] sconklin, ara, marjo - does that match your understanding too? [16:36] yes [16:36] Yes, that's the way I read the Nattyinterlock schedule, and that's what we're targeting. [16:36] skaet: why, "no later than this Friday"? [16:37] skaet: usually, QA testing starts on Mondays [16:37] marjo, beta-1 will be out, and code will be ready. [16:37] skaet: ack [16:37] thanks marjo. [16:37] .. [16:37] any other questions? [16:38] [TOPIC] general SRU status - pitti [16:38] New Topic: general SRU status - pitti [16:38] still need to schedule a training session with SpammapS [16:38] last time we had one the queues were empty, and then the beta-1 rush came in the way [16:39] there is a high-urgency bind9 update which we need to rush through, for bug 651875 [16:39] Launchpad bug 651875 in bind9 (Ubuntu Lucid) "Bind 9.7.0-P1 validation errors" [Medium,Confirmed] https://launchpad.net/bugs/651875 [16:39] (Daviey is on it now) [16:39] otherwise, business as usual [16:39] .. [16:39] thanks pitti [16:40] any one have questions? [16:40] [TOPIC] OEM priorities [16:40] New Topic: OEM priorities [16:40] any one around to represent OEM since vanhoof is out? smagoun? [16:40] skaet: I'm here [16:41] any issues to flag, and priorities we need to be aware of? [16:41] skaet: I confess I've not been following the meeting though - is this specifically OEM priorities for Natty? [16:41] smagoun, for maverick, lucid, and other stable releases [16:41] (everything except natty ;) ) [16:41] skaet: The SRU cycle has been preempted by 11.04 testing, which has caused a bit of fuss in OEM but we've worked around it. [16:42] skaet: We have a couple of bugs in the -proposed kernel, we do want them to see the light of day eventually ;) [16:43] smagoun, the fixes in proposed will be going through in week after this one. [16:43] skaet: I think the (natural) tension of having 1 team test new development (11.04) and maintenance needs to be addressed organizationally, which makes it a good topic for the UDS timeframe [16:43] smagoun, agreed [16:44] skaet: Going through, as in released to -updates? [16:45] smagoun, per the interlock, that's targeted for 4/7. [16:45] after that next window for fixes to go to updates is end of first week of may. [16:46] all changes for that one will need to be in -proposed by 4/22. [16:46] skaet: ok, thanks. A couple people around here interpreted bjf's mail as there being nothing new into -updates from now until May. Glad to hear that's not the case. [16:46] https://wiki.ubuntu.com/NattyReleaseInterlock [16:46] .. [16:46] thanks smagoun [16:46] any other questions? [16:47] not right now, thanks [16:47] I meant anyone else have questions for you ;) will move on though since I don't see any hands [16:47] [TOPIC] Support priorities - martins [16:47] New Topic: Support priorities - martins [16:48] * skaet not seeing martins in the channels though today. [16:48] anyone have concerns from support? representing martin? [16:48] [TOPIC] New business, last chance for general questions? - all [16:48] New Topic: New business, last chance for general questions? - all [16:49] does anyone want me to summarize what the plan is for the next month, or is it pretty clear now from the discussions? [16:49] summary! summary! go skaet, go! [16:50] :) [16:50] kernel (maverick, lucid) -> proposed 3/25 [16:50] verification in progress this week [16:51] hw cert/qa - 4/1-4/7 [16:51] kernel (maveric, lucid) -> update 4/7 [16:51] kernel ( maverick, lucid?)-> proposed 4/22 [16:52] verification 4/25-4/29 [16:52] hw cert/qa - 4/29 - 5/5 [16:53] kernel (maverick, lucid? ) to update 5/5 [16:53] after that we're at UDS, and revisit the cycle for the rest of Oneiric. [16:53] skaet: ack [16:53] sounds good to me [16:54] sconklin, bjf - ok? [16:54] reading [16:55] yes, I think that matches everything that we talked about earlier, and I'm happy to see the possibility that Lucid will get through also [16:55] .. [16:55] ok, thanks all. I think we've got this sorted then. [16:55] good meeting. [16:55] skaet: thx [16:55] next meeting is 4/11. [16:56] #endmeeting [16:56] Meeting finished at 10:56. [16:56] thanks marjo, ara, bjf, sconklin, pitti, smagoun [16:56] Thanks skaet! [16:56] thanks skaet! [16:58] thanks all === bjf[afk] is now known as bjf === Thermi is now known as thermi === thermi is now known as Thermi [18:06] hello [18:06] hi [18:06] let's get started [18:06] * sbeattie waves [18:07] #startmeeting [18:07] Meeting started at 12:07. The chair is jdstrand. [18:07] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:07] The meeting agenda can be found at: [18:07] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:07] [TOPIC] Review of any previous action items [18:07] LINK received: https://wiki.ubuntu.com/SecurityTeam/Meeting [18:07] New Topic: Review of any previous action items [18:08] sbeattie uploaded apparmor 2.6.1. great work sbeattie, thanks! [18:08] jdstrand: thanks for sponsoring! [18:08] I (finally) got arround to looking at blackhat/defcon registration, and that is underway now [18:08] sbeattie: sure thing :) [18:09] [TOPIC] Weekly stand-up report [18:09] New Topic: Weekly stand-up report [18:09] I'll go first [18:09] so, last week I didn't get to a bunch of stuff I thought I would, and this week is a short week for me [18:09] I will be off friday and then next monday and tuesday [18:10] I am on triage this week [18:10] I hope to finish testing the openldap and libvirt updates [18:10] and I expect some archive admin work for beta [18:10] I'll try to get to the other stuff I said I'd do last week as I have time [18:11] that's it from me [18:11] mdeslaur: you're up [18:11] I am currently testing packages for a bunch of security updates I've prepared last week [18:11] I'll be publishing them this week if all goes well [18:11] beyond that, I'll go down the list [18:11] oh, and if this is beta week, I'll do some iso testing also [18:11] that's it from me. [18:12] -> sbeattie [18:12] I was on community last week, sponsored a couple of packages (dtc, loggerhead) [18:12] I'm in the happy place this week, so I'm looking for updates to pick up (was thinking postfix) [18:13] I think that's all for me. [18:13] Oh, yeah, iso testing. [18:13] * sbeattie has one system left to upgrade to natty as well. [18:14] * sbeattie -> micahg [18:14] so, as jdstrand added to the wiki, I'm cleaning up after the comodo mess [18:15] nss, qt4-x11, ca-certificates (maybe) [18:15] there's a chromium update, but we're blocked on an upstream regression [18:15] and I have ISO testing [18:15] micahg: is there a workaround for that? ie, can we just fallback to the previous behavior? [18:16] jdstrand: well, there's a workaround, but it's flaky IMHO [18:16] was going to discuss with you further after the meeting [18:16] micahg: right, --detect=auto or something. I meant something where we can just have the old upstream behavior [18:16] s/upstream// [18:17] jdstrand: well, I have to see exactly what the old behavior was to answer that :) [18:18] micahg: ok. as you know, fta can probably help there. I don't think we can publish chromium in good conscience with that regression [18:18] so, possibly, fta mentioned possibly working around it [18:18] micahg: alternatively, I wonder if we can snag fta's previous update for the comodo fixes and push that into the archive [18:18] micahg: then wait for upstream to fix the regressino [18:19] (assuming there isn't a good way to deal with the current version that has the additional security fixes) [18:20] I'll look into that [18:21] ok [18:22] micahg: did you have anything else? [18:22] no, I think that's it for me [18:22] thanks [18:22] [TOPIC] Miscellaneous and Questions [18:22] New Topic: Miscellaneous and Questions [18:23] Looks like self-evaluations are done. I need to do my part now (I have a couple weeks) [18:23] all work items tied to natty's release are completed. Great job everyone! :) [18:24] that's all I have [18:24] does anyone have any other questions or items to discuss? [18:24] o/ [18:24] micahg: go ahead [18:25] when does the review for the testing libraries (QRT) start? next week? [18:25] https://wiki.ubuntu.com/SecurityTeam/ReleaseCycle#Regression%20Testing [18:26] yep, ok :) [18:26] ^ that says kernel and glibc should be happening now [18:26] the rest fall port-beta [18:26] s/port/post/ [18:27] kees and/or sbeattie have traditionally done the kernel/glibc ones [18:27] and I'm pretty sure they have been done all the way along [18:28] any other questions? [18:28] ok. thanks everyone! [18:28] #endmeeting [18:28] Meeting finished at 12:28. [18:28] thanks jdstrand [18:30] thanks jdstrand! [18:31] sure! :) === em is now known as emma [19:58] any chance DMB will get quorum today? [19:59] I am partially here [19:59] * stgraber too [19:59] just got out of a meeting and have quite a lot of stuff to do now but will follow the meeting for votes and stuff [20:00] that's if we manage to get quorum [20:00] * bdrung_ is here, but very tired. [20:00] bdrung_: as long as you're not cranky.. thats ok. ;) [20:01] maco, cody-somerville, persia, geser: ping [20:01] :) === apachelogger is now known as javalogger [20:02] SpamapS: not cranky, just slow and unemotional [20:02] Hi. [20:02] I would propose not approving SpamapS so we still get to make him do useful stuff in exchange for sponsorship. [20:02] ;-) [20:03] :-) [20:03] who wants to chair? [20:03] Wow. 8 applications? Geez. I dunno if we'll get through them all. [20:03] I am on my phone and in a pub so no good. [20:03] * geser waves [20:04] please do not pay attention to scottk he is a master extortionist ;) [20:05] ScottK: will SpamapS do useless stuff if he gets upload rights? [20:05] extorionist/efficient distorbutor of necessary work. [20:05] ScottK: all a matter of perspective. :) [20:05] geser: No, but I'll lose leverage to get him to work on my stuff. [20:06] geser: I will occasionally still play Angry Birds if I have upload rights.. ;) [20:06] hi [20:06] can we get started? === Ursinha is now known as Ursinha-lunch [20:06] hrw, hey [20:06] * cody-somerville volunteers to chair. [20:06] * hrw just arrived at home - 21:07 here [20:07] ty [20:07] Do we have quorum? [20:07] yep [20:07] yes [20:07] #startmeeting [20:07] Meeting started at 14:07. The chair is cody-somerville. [20:07] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [20:07] [TOPIC] Review of previous action items [20:07] New Topic: Review of previous action items [20:08] * Emmet Hikory to organise the selection process for DMB renewal [20:08] done [20:08] Ack. [20:08] [TOPIC] Administrative Matters [20:08] New Topic: Administrative Matters [20:09] [TOPIC] Administrative Matters: Review progress of probationary period of Marco Rodrigues [20:09] is the mailing lists admin issue now resolved? [20:09] New Topic: Administrative Matters: Review progress of probationary period of Marco Rodrigues [20:09] So, I've unfortunately dropped the ball on this. It had been my intention to have already sent an e-mail report out weeks ago. [20:10] geser: mostly, I think someone from the tb sould sort out the dmb admin soon [20:10] mailed today. [20:11] I still intend to send an e-mail. To summarize however, I'm unsure if the probation period has been entirely effective. [20:11] Though there were a few occasions early on where Marco did not follow the agreement by participating in discussions in #ubuntu-motu. [20:12] And I've not yet processed anything he has submitted to me that I was actually able to sponsor due to problems. [20:12] what kind of problems? [20:13] He requested a sync but did not test build it in Ubuntu. It turned out the package FTBFS in Ubuntu. I later found there was even already a bug report open regarding it. [20:14] Furthermore, doing an actual debdiff resulted in additional delta not mentioned in the package changelog and that was not mentioned in his request. [20:15] It appears the decision to request the sync was based entirely on examination of the package changelogs. [20:17] [TOPIC] Administrative Matters: Membership renewal policy for delegated teams [20:17] New Topic: Administrative Matters: Membership renewal policy for delegated teams [20:17] how many requests from Marco did you had to review? [20:18] oops [20:18] geser, It submitted 5 in total. The last one sent to me was January 25th. [20:18] *He [20:19] He sent me an e-mail February 7th regarding one of the requests I had not yet processed. The request was sufficiently old to ping me about it. [20:20] did you had any problems besides technical issues? [20:21] did he repeat mistakes? === bdrung_ is now known as bdrung [20:21] I guess we can discuss this after your detailed report per mail, let's move to the next topic as the agenda is long [20:22] * bdrung nods. [20:22] He's been involved in Ubuntu development since 2007, IIRC. Basic stuff like test building he should know by now. [20:22] currently the members of delegated teams need to have their membership renewed by an admin. I don't see what the point of this is, seems to be busy work to me. I suggest we allow members of delegated teams to renew themselves. [20:22] sorry for being terse again, on phone [20:22] i am fine with this change. [20:23] ScottK: true, and this sound like the kind of the problems in the past [20:23] bdrung, He participated in #ubuntu-motu a few times even after reminder that it violated the agreement. [20:23] shall we just vote? [20:23] yes [20:24] geser: Agreed. [20:24] greping my logs I actually see he said something to Laney on the 20th of January even [20:24] (in #ubuntu-motu) [20:24] Jan 20 13:03:39 Laney: check collab-qa for udd scripts, there is a rcbugs for debian -> ubuntu, it could be adapted easily. [20:24] Laney, on the renewal policy? [20:24] yes [20:25] Aye. [20:25] [VOTE] Allow members of delegated teams to renew themselves. [20:25] Please vote on: Allow members of delegated teams to renew themselves.. [20:25] 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:25] E.g. /msg MootBot +1 #ubuntu-meeting [20:25] +1 [20:25] +1 received from bdrung. 1 for, 0 against. 0 have abstained. Count is now 1 [20:25]