=== Andre_Gondim is now known as Andre_Gondim-afk === Gunblade__ is now known as GunbladeIV === thekorn_ is now known as thekorn === a|wen_ is now known as a|wen === MaWaLe1 is now known as MaWaLe === thunderstruck is now known as gnomefreak === thunderstruck is now known as gnomefreak [13:59] hello [13:59] hi :) [13:59] howdy [13:59] * lool waves [13:59] slangasek: morning! [13:59] morning [14:00] good morning [14:00] \o <--- Here after all ($WORK meeting cancelled). [14:00] morning [14:00] * sbeattie waves [14:01] hiya [14:01] pgraner, davidm, Riddell, Hobbsee: ping [14:02] slangasek: here [14:02] hi :) [14:02] slangasek: 56 minutes ago Riddell said he'd be out for an hour on #kubuntu-devel. [14:02] #startmeeting [14:02] Meeting started at 09:02. The chair is slangasek. [14:02] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [14:02] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-03-27 [14:02] LINK received: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-03-27 [14:02] ScottK: ok [14:03] [TOPIC] Outstanding actions [14:03] New Topic: Outstanding actions [14:04] just a few straggler items here [14:04] lool: 303232 - will you have a chance to open the per-lib tasks, or should I go ahead and do it? [14:05] slangasek: I did, sent you the list [14:05] and do you guys need help with the actual lib changes? [14:05] slangasek: I'm disappointed your not procmail-ing to your dreams! [14:05] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-vfp [14:05] [LINK] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-vfp [14:05] LINK received: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-vfp [14:05] slangasek: Well in theory no, in practice help is welcome [14:06] ah, separate bugs - these aren't targeted to jaunty yet? [14:07] oh no, will milestone them now, sorry [14:07] I was assuming the gcc-4.3 task on bug #303232 should be closed once those lib tasks are open [14:07] Launchpad bug 303232 in gcc-4.3 "armel gcc default optimisations" [High,Confirmed] https://launchpad.net/bugs/303232 [14:07] slangasek: I think I'll unmilestone it and make it a bug to discuss gcc opts for karmic [14:07] * slangasek nods [14:08] Ah the gcc one is unmilestoned [14:08] Can't untrack it for jaunty [14:08] lool: 'wontfix' the jaunty task [14:08] thanks [14:08] pgraner: you said apw and pitti were working on the kernel suspend/resume tagging - is there a bug number for tracking that? [14:09] apw just said he'll file one with what needs to be changed [14:09] slangasek: I should have it in a few minutes, I'll send it over to you [14:09] ok [14:09] should by done by next week [14:10] last item on the list is mine; we got the CDs back down to size for beta through a combination of langpack rebasing and more heroic efforts by seb128, but we're not really any closer to having a good way to track where our CD space went in the first place [14:11] slangasek: I would bet on GNOME translated documentations [14:11] ie extra localized screenshots [14:11] would it help to get cd-size-analysis fixed not to need packages still in cdimage's mirror? [14:11] (vfp bugs milestoned and targetted to jaunty) [14:11] cjwatson: yes; I'm going to spend some quality time with the build logs early next week to see if I can extract all the information I need for this [14:11] lool: thanks [14:12] so that's it for carry-overs [14:13] [TOPIC] Future issues expected to impact the release [14:13] slangasek, https://bugs.launchpad.net/ubuntu/+source/apport/+bug/349621 [14:13] New Topic: Future issues expected to impact the release [14:13] Ubuntu bug 349621 in apport "real kerneloops and suspend/hibernate/resume bugs are hard to separate" [Undecided,New] [14:13] apw: great, thanks [14:13] I just milestoned a new bug, Bug #348704, since (that I know of) it breaks update-notifier-kde for upgraders. [14:13] Launchpad bug 348704 in python-qt4 "/var/lib/python-support/python2.6/dbus/mainloop/qt.so missing after upgrade" [High,Confirmed] https://launchpad.net/bugs/348704 [14:13] OMG, who put bug #1 back on the jaunty list [14:13] https://bugs.launchpad.net/ubuntu/+bug/1 (Timeout) [14:14] It's got me flumoxed, so I'd appreciate it if someone like doko or maybe mvo_ could have a look. [14:15] mvo_: do you have time to look at that? [14:16] * slangasek targets the bug as well [14:16] nothing new for that topic from desktop, for the record (https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus is up to date) [14:16] ScottK: you also brought up clamav as an issue. Do we need to talk about that further here? [14:16] [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [14:16] LINK received: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [14:16] It's an issue. [14:17] I'm afraid we may have to choose between releasing with an oboslete clamav or with some broken rdepends. [14:17] Given what it does, not releasing with the current one is not good. [14:17] how obsolete is obsolete? [14:18] ScottK: how often does clamav break ABI? [14:18] ScottK: IOW, if we'd need to do another update for jaunty-updates, would we need to go through that rdepends rebuild dance again, or was it more like an one-time change? [14:18] cjwatson: one major version (0.94.2 versus 0.95) behind. I can (but haven't) quantified how many virus types we'll miss [14:18] pitti: Every major version they break it. [14:19] They did sort of promise this is the last time and they've never done that before. [14:19] All the libclamav rdepends do need changes to work with 0.95. All the clamd users are fine. [14:20] I should know by the middle of next week better where we are. [14:20] on the flip side of pitti's question, we have tracked clamav in -backports in the past rather than in -updates, so if the reverse-deps couldn't catch up it's not as though we don't have a way to make 0.95 available to jaunty users? [14:21] That's true. [14:21] We have also pushed -backports to -security when the time came to keep the maintenance burden manageable (only in Universe). [14:21] slangasek: I can have a look at the python-qt4 issue [14:22] (I guess I'm as busy as everyone else) [14:22] I have a plan for the tech board on my TODO to write up about that .... [14:22] ScottK: I'm happy to let you make the decision regarding which way we go on the obsolete vs. rdeps question; let us know next week what we can do to help? [14:22] python-qt4> doko is away for a few days unfortunately [14:22] * slangasek nods [14:22] mvo_: ok, subscribed you [14:22] slangasek: OK. Thanks. [14:23] ScottK: any other things to discuss while you have the floor? [14:24] KDE 4.2.2 was tagged yesterday. [14:24] It'll get released ~tuesday next week. [14:24] sounds good [14:24] They've been very good about bugfix only in the third digit updates, so we're operating on the assumption this goes in. [14:24] That's it. [14:24] * slangasek nods [14:24] I have a concern I'd like to raise, from while I was thinking about release notes [14:24] cjwatson: go ahead [14:25] I went and looked at http://www.ubuntu.com/getubuntu/releasenotes/810 last night and noticed that there are at least some things there that we never properly targeted to jaunty and haven't fixed [14:25] I think we should make a systematic effort to ensure that everything fixable there gets fixed [14:25] cjwatson: good call [14:25] (after cjwatson, I'll do around the rest of the teams in a circle to make sure everyone has a chance to comment) [14:25] bug 290234 was the one I particularly noticed, though I've pushed up a branch fixing that one for mvo's review [14:25] Launchpad bug 290234 in apt "Intrepid: Netboot locks up at 2% installing the selected edubuntu desktop" [High,In progress] https://launchpad.net/bugs/290234 [14:25] s/do around/go around/ [14:25] cjwatson: can we put that onto a checklist somewhere so that release noted items for release x get targeted for x+1 as SOP? [14:26] mdz: good idea, I'll put it on NewReleaseCycleProcess [14:26] [ACTION] cjwatson to document release-targeting of previous release release-notes items for NewReleaseCycleProcess [14:26] ACTION received: cjwatson to document release-targeting of previous release release-notes items for NewReleaseCycleProcess [14:27] cjwatson: since you're already partway through, can you also take care of finishing the release notes review in this case and targeting anything else that's outstanding? [14:27] suckered [14:27] ok [14:27] (I've done the NewReleaseCycleProcess change) [14:27] [ACTION] cjwatson to complete review of 8.10 release notes to identify jaunty targets [14:27] ACTION received: cjwatson to complete review of 8.10 release notes to identify jaunty targets [14:28] is there any other similar list of major issues that we might have forgotten about? [14:28] not that I'm aware of [14:29] I have been sucking in the technical overview errata after each milestone [14:29] bugs tagged regression-release, perhaps. [14:30] (though alas the current set needs more triage, as I've been focusing on the regression-potential tagged bugs) [14:31] sbeattie: can you triage them and let us know about any that need targeting yet, or should we get more hands on triaging? [14:31] I'll talk with the rest of the QA team about getting more triage love for them. [14:32] feel free to action me on tha.t [14:32] [ACTION] sbeattie to follow up with QA team about getting attention on the regression-release bugs [14:32] ACTION received: sbeattie to follow up with QA team about getting attention on the regression-release bugs [14:32] maybe some announcement regarding regression-{potential,release} might refresh memory of some devs? (/me included *g*) [14:33] sistpoty|work: okay; heno did one recently, I thought, but we can do it again. [14:33] sbeattie: :) [14:33] [TOPIC] QA team [14:33] New Topic: QA team [14:33] * heno nods - let's do that [14:33] sbeattie, fader, heno: anything else we need to discuss from your corner? [14:34] I just want to mention that we got a large number of 'failed' results in the most recent hardware tests, but it's because there's a checkbox test breaking [14:34] also as a reminder, I have been assigning regression-potential bugs to teams; please look at the team-assigned reports at http://qa.ubuntu.com/reports/team-assigned/ [14:34] fader_: noted, thanks [14:34] There's a bug on it and it should be resolved pretty quickly but I didn't want anyone to panic when looking at the report :) [14:34] fader_: do you guys have some hardware with intel 8x5 chips, with x == {4,5,6}? [14:35] pitti: Is this about the X issues that Bryce is working on? [14:35] fader_: right, -intel driver not working on some/all i845/i855 [14:35] bug #304871 [14:35] Launchpad bug 304871 in xserver-xorg-video-intel "[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)" [Unknown,Confirmed] https://launchpad.net/bugs/304871 [14:35] ScottK's feedback was that the problem was resolved for him with the beta [14:35] pitti: From last week's meeting I did test with i865 and it WFM. [14:36] pitti: I'm looking through the hardware list to find the machines that have those chipsets, as we don't currently have a good automated way to find that out [14:36] fader_: many thanks [14:36] I'll coordinate with him to get him that list and any other details he needs [14:36] np :) [14:37] We expect a spike in bug reports after Beta and would appreciate it everyone gave and hand in triaging new bugs [14:38] we will focus mainly on that next week [14:38] heno: any particular areas that would most helpful to look at? [14:38] bdmurray is preparing a list of 'bugs filed since beta' [14:38] rickspencer3: first of all bugs for packages each person cares about [14:39] noted [14:39] the installer usually gets a fresh influx too [14:39] (that's it from QA) [14:40] [TOPIC] Mobile team [14:40] New Topic: Mobile team [14:40] (pitti already said 'nothing new for desktop' :) [14:40] lool: anything you need to raise? [14:40] (may I dump my usual status?) [14:40] yes [14:41] list of specs and bugs on our radar ; current high-level status per topic: [14:41] - UNR good shape except for intel graphics regression on eeepcs (349314, 344443) [14:41] [LINK] https://wiki.ubuntu.com/MobileTeam/Roadmap [14:41] LINK received: https://wiki.ubuntu.com/MobileTeam/Roadmap [14:41] lool: I'm aware that there are quite a few things where the mobile team is waiting for foundations to fix stuff, and I'd like to make sure nothing is slipping through the cracks. Is MobileTeam/Roadmap the thing we should be monitoring? [14:41] pgraner: Mind if I milestone that linux bug for jaunty? [14:41] lool: alternatively, if you routinely target the relevant bugs to jaunty, that's fine too [14:41] cjwatson: It's a good mean to put things on our radar [14:41] cjwatson: So happy if you put something there which we should keep an eye on [14:42] lool: no, I meant the other way round [14:42] lool: things that are already on your radar that should be on ours [14:42] cjwatson: Then no, it's where we track what we have to do [14:42] cjwatson: I guess we should use bugs and subscribe to them ourselves when we're blocked by foundation stuff [14:42] lool: yea milestone it [14:42] in that case, if you could target relevant bugs to jaunty, that's the best way to make sure we don't forget [14:43] It's a good question, we often wonder how to track e.g. a kernel issue which affects the team which we'd like to keep an eye on but we can't do anything about ourselves [14:43] lool: for example, should bug 347350 be RC for jaunty? [14:43] Launchpad bug 347350 in oem-config "oem-config-firstboot does not fit in 1024x600" [High,Triaged] https://launchpad.net/bugs/347350 [14:43] cjwatson: Well I was personally reluctant to push for too high standards in screen resolution, but that's my personal position; it would be high on our list of things we'd like to see fixed on jaunty though [14:44] (general focus on playing nicer with small screens basically) [14:44] I'll target it and leave a comment to that effect [14:44] pgraner: thanks, done [14:44] cjwatson: I'm happy to comment on any bugs where you need guidance on priority/importance, or raise them in my team [14:44] - MID image is okay-ish; needed extra care for beta [14:45] - armel netbook images: pretty bad beta outcome with versatile and iop32x broken [14:45] , so only ixp4xx to release; imx51 netboot will be added with next d-i upload [14:45] - armel's "iMX51 Babbage": first image released in beta required extra hacks; working on merging everything in archive; lots of hardware support issues with the kernel which need FSL patches (wired network, USB, wifi); need testplan [14:45] - VFP libs, NEON: in progress; list of bugs covered earlier [14:45] - other milestoned bugs: generally coming back to focusing on them after the bab [14:45] bage/beta push [14:45] - Poulsbo drivers: late, no progress yet on finding out why the intrepid drivers don't work for us but work for Intel; looking harder and harder to get in jaunty; Intel claimed they targetted mesa 7.3, so a mesa update at this point could i [14:45] n theory impact these drivers, but given that's 7.3 => dev and 7.4 => stable it's not supposed to [14:45] (sorry vim is unhappy today) [14:45] - touchscreen support: ogra didn't have time to work on this due to babbage, and we lack support for a bunch of them [14:46] lool: what kind of 'not work' did you get with poulsbo? [14:46] http://paste.ubuntu.com/138987/ is the same dump, but readable [14:46] LINK received: http://paste.ubuntu.com/138987/ is the same dump, but readable [14:46] slangasek: StevenK says the GL support doesn't work at all; Intel says it does [14:47] Like glxgears not even working [14:47] ok [14:47] I'm a bit worried that we're at that point for the drivers [14:47] just asking because mythbuntu was having issues with mesa, superm1 uploaded a fix to revert a couple of patches post-beta [14:47] but it doesn't sound like it's related [14:48] No, I'm mentionning the state of intrepid [14:48] oh, ok [14:48] Because the packaging was supposed to be copied from the intrepid one when complete [14:48] right [14:49] So the chain of actions which would give us jaunty drivers is a bit scary: a) fix 3D b) agree on way forward for jaunty packaging (stevenk/bryce) c) push to jaunty and test [14:49] right [14:49] However on the mesa side, it's not looking happy with DRI ATM [14:50] This is not really related to mobile, but elisa upstream contacted me about a regression in mesa which is fixed in 7.4RC2 [14:50] bug #349127 [14:50] Launchpad bug 349127 in mesa "Elisa displays video with greenish/purplish colors" [High,Incomplete] https://launchpad.net/bugs/349127 [14:50] And they say it affects other; I poked bryce to check whether that was worth tracking for jaunty; I personally think it is if we have a reviewable patch [14:51] * slangasek targets it to jaunty pre-emptively [14:51] are there questions from anyone with the mobile status? anything I forgot to cover? [14:51] I think that covers it for me, thanks [14:52] [TOPIC] kernel team [14:52] New Topic: kernel team [14:52] slangasek: We have a Broadcomm STA driver update landing soonish that fixes lots of reported issues. [14:52] slangasek: LP 334994 there is a race in the kernel somewhere which is tricky to trigger on real hardware which leads to the kernel not clearing down some sysfs state. [14:52] Launchpad bug 334994 in linux "Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with -EEXIST, don't try to register things with the same name in the same directory" [High,In progress] https://launchpad.net/bugs/334994 [14:52] the Broadcom should already be in, I think [14:53] slangasek: apw is on the RAID one [14:53] ack [14:53] * slangasek nods [14:53] other than those its the usual ARM goodness [14:54] Thats it for kernel team [14:54] pgraner: In general, babbage status is pretty bad kernel side [14:54] bug #343254, hmm, didn't I see that discussed in the linux changelog? [14:54] Launchpad bug 343254 in linux "pulseaudio: alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large" [High,In progress] https://launchpad.net/bugs/343254 [14:54] I know kernel team is waiting for FSL patches, but I jsut want to raise it that we really care a lot if you can get them in [14:54] lool: hense my comment about ARM [14:54] pgraner: Yup, echo-ing your concerns with my specific issues :) [14:55] lool: Freescale is the issue unfortunately [14:55] Ack; I think with the beta image we have a better basis to demo our problems [14:56] The other non-FSL thing would be the versatile image which was broken just before beta [14:56] I don't know whether it's worth fighting apparmor there; I don't think it ever worked for us there; happy if you fix it but I don't mind disabling it on verstaile [14:56] slangasek: don't know about that one, dtchen has been working it [14:57] pgraner: yep; pinged him [14:57] Hmm indeed, I'm having pulseaudio issues myself [14:57] lool: we just got it AA working for the imx51 we'll look at it on versatile. [14:58] pgraner: Yes, I think it was turned on in versatile because it was believed the fix would also allow it to work under versatile [14:58] lool: bug number? [14:58] versatile/apparmor is already targeted; bug #348835 [14:58] Launchpad bug 348835 in linux "versatile: OOPS in apparmor" [High,Triaged] https://launchpad.net/bugs/348835 [14:58] 348835 [14:58] lool: ack, we'll get on it [14:59] thanks [14:59] are there any other actionable issues wrt ARM, or that we need to get on the bug list? [14:59] The FSL dependent ones are not milestoned, the rest is properly milestoned [15:00] slangasek: we are working to the bug list and working with Freescale so it will go up to kernel freeze [15:01] * slangasek nods [15:01] cjwatson: was there anything else we needed to discuss for foundations, or are we covered? [15:01] [TOPIC] Foundations team [15:01] New Topic: Foundations team [15:02] I think I covered it [15:02] ok, thanks [15:02] [TOPIC] Server team [15:02] New Topic: Server team [15:02] hi [15:02] heya [15:02] a couple of release critical bugs in eucalyptus. [15:02] bug 347622 [15:03] Launchpad bug 347622 in eucalyptus "in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks" [Critical,Confirmed] https://launchpad.net/bugs/347622 [15:03] bug 347629 [15:03] Launchpad bug 347629 in eucalyptus "in SYSTEM mode, CLC tries to discover elastic IPs from CC even though elastic IP support is not enabled in SYSTEM mode" [Critical,Confirmed] https://launchpad.net/bugs/347629 [15:03] we are also watching bug 334994 which the kernel team is working on. [15:03] Launchpad bug 334994 in linux "Degraded RAID boot fails: kobject_add_internal failed for dev-sda1 with -EEXIST, don't try to register things with the same name in the same directory" [High,In progress] https://launchpad.net/bugs/334994 [15:04] * slangasek nods [15:04] it affects vm's, however, we are not how valid a usecase. apart from testing, software raid has in vm's [15:05] That's all that new. [15:05] ok, thanks [15:05] I think that's it, then [15:05] anything else from anyone? speak now or hold your peace until the same time next week [15:05] (or until #ubuntu-devel) [15:06] #endmeeting [15:06] Meeting finished at 10:06. [15:06] thanks, folks [15:06] Thanks [15:07] thanks everyone === Tonio__ is now known as Tonio_ [15:52] hello MTecknology, how are things? [15:52] I am pinging you re. my membership to "Official Ubuntu Members" [15:52] yup, I'm here [15:53] I received an email suggesting to meet here [15:53] Just an FYI, the group membership is for official Ubuntu members only [15:53] sure [15:53] are you a member? [15:54] yes, I am muharem@ubuntu.com but my linkedin accont is tied to a different email [15:54] can you give me a link to your profile? [15:54] MTecknology: https://edge.launchpad.net/~al-maisan [15:55] I don't see you having an @ubuntu.com email addy [15:56] just a sec [15:56] al-maisan: actually, give me a minute - I'm discussing something with someone right now [15:56] sure [15:57] I've been basing it off of membership to ~ubuntumembers. You're the second canonical employee not an ubuntu member - I'm not 100% sure what I should be doing with this :P [15:57] OK [15:57] take it easy [15:58] MTecknology: Do you have any idea how many copies of your mail some people got? [15:58] I assumed I am a member [15:58] You're approved, but I'll need to think over that whole thing again. You should apply for membership :) [15:58] it'll make it easier for me :) [15:59] ScottK: 2 should be the max, and that should only have been to a few [15:59] MTecknology: will do. [15:59] al-maisan: I assume you know where to apply at? [15:59] * al-maisan just saw this: https://wiki.ubuntu.com/Membership [15:59] yup - thansk for chatting with me [16:00] MTecknology: Three for me. [16:00] MTecknology: thank you. [16:00] ScottK: what route did they all take? :S [16:02] MTecknology: One for Kubuntu members, one for Ubuntu members, and one for Ubuntu core-dev. [16:03] ScottK: .... Oh sh**. I forgot that other teams are members of the team [16:03] I'm going to file a bug about that happening. I'm sorry about that. [16:04] MTecknology: Well that's fine, but I also believe you're abusing Launchpad. I think it's grossly offtopic to use the contact a user feature to promote a social network. [16:05] I've got it on my TODO to mail you, but since I saw you here .... [16:06] ScottK: I was trying to figure out a better way to hit the "target market", but Icouldn't figure one out. A few people enjoyed that I did it that way actually. [16:07] MTecknology: I think your post to planet did that fine. [16:07] oh [16:07] ScottK: I am sorry - forgive me? :) [16:08] MTecknology: If I've got a really cool Ubunt t-shirt I want to sell to ubuntu members, is it appropriate for me to reach my target market this way? [16:08] MTecknology: I suppose, but just understand that some people are very sensitive about unwanted intrusions in their inbox. [16:09] ScottK: ya. I'll think about it a little longer next time [16:10] * ScottK nods [16:11] ScottK: on the other side of the fence though - it's up to 88 members now [16:11] MTecknology: So spamming is justified based on it works? [16:12] ScottK: for some people that make a living off it :P - but no, that was just a side comment [16:12] I'll run away now [16:12] on the other side of the fence comes across as justification to me. [16:12] OK === fader_ is now known as fader|lunch === beuno_ is now known as beuno === fader|lunch is now known as fader_ === Andre_Gondim-afk is now known as Andre_Gondim === beuno_ is now known as beuno === Andre_Gondim is now known as Andre_Gondim-afk === Andre_Gondim-afk is now known as Andre_Gondim === Andre_Gondim is now known as Andre_Gondim-afk === bazhang_ is now known as bazhang === thunderstruck is now known as gnomefreak