=== JayFo is now known as JFo
=== asac_ is now known as asac
=== Yos_ is now known as Yos
=== doko__ is now known as doko
=== mac_v_ is now known as mac_v
=== vuntz_ is now known as vuntz
=== fader|away is now known as fader_
=== asac_ is now known as asac
=== freeflyi1g is now known as freeflying
[15:58]  * slangasek waves
[15:58]  * JamieBennett waves back
[15:59]  * marjo waves
[15:59] <pitti> o/
[15:59] <pgraner> pgraner: \o/
[16:00] <njpatel> hey
[16:00] <ttx> o/
[16:01] <tedg> Howdy
[16:01]  * apw zones in
[16:02] <slangasek> asac, ogra, Riddell, jiboumans, jdstrand: ping
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> slangasek, There is already a meeting in progress.
[16:02] <jiboumans> slangasek: \o
[16:02] <slangasek> hmm
[16:02] <JamieBennett> I'm covering for asac, he's on vacation
[16:02] <slangasek> JamieBennett: ok
[16:02] <marjo> slangasek: received same mootbot message after netsplits this week
[16:02] <pitti> killall -HUP MootBot
[16:03] <jiboumans> same here
[16:03] <slangasek> right, no bot for us then
[16:03] <apw> slangasek, try and #endmeetting, he might tell us who
[16:03] <slangasek> #endmeeting
[16:03] <slangasek> no such luck, then
[16:04] <slangasek> ScottK: also ping
[16:04] <Riddell> hi
[16:04] <ScottK> \o
[16:04] <jiboumans> #endmeeting
[16:04] <slangasek> [TOPIC] Actions from previous meeting
[16:04] <slangasek>  * ScottK and RoAkSoAx to discuss hand-off of part of the binary removal spec
[16:04] <ScottK> Handed off and he's working on it.
[16:04] <slangasek> excellent
[16:05] <ScottK> Didn't get any updates recently.
[16:05] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-18, btw
[16:05] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-18, btw
[16:06] <slangasek> ScottK: he'll ask if he has doubts, I guess?
[16:06] <ScottK> Yes, I would hope.
[16:06] <ScottK> I'll ping him when I see him.
[16:06]  * slangasek nods
[16:06] <slangasek> [TOPIC] QA Team
[16:06] <marjo> pitti: hope you like these results
[16:07] <pitti> :)
[16:07] <slangasek> marjo: did we get the installer problem resolved, so fader_ could make progress on server testing?
[16:07] <marjo> * Hardware testing
[16:07] <marjo> Netbooks:
[16:07] <marjo>         passed:   12 (92%)      failed:    1 ( 8%)      untested:  0 ( 0%)
[16:07] <marjo> Laptops:
[16:07] <marjo>         passed:   26 (100%)     failed:    0 (  0%)  untested:  0 (  0%)
[16:07] <marjo> Servers:
[16:07] <marjo>         passed:   32 (63%)      failed:   19 (37%)    untested:  1
[16:07] <marjo> Notes:  bug 494052 continues - fix made it into the installer yesterday.
[16:07] <marjo> ev (evan dandrea) has fixed the build. debian-installer (20081029ubuntu77)
[16:07] <ubottu> Launchpad bug 494052 in linux "bnx2 driver cannot find firmware" [Medium,Fix released] https://launchpad.net/bugs/494052
[16:07] <marjo> Will retest.
[16:07] <marjo> slangasek: does that answer your question?
[16:07] <slangasek> yes :)
[16:08] <marjo> Desktops:
[16:08] <marjo>         passed:   12 (100%)     failed:    0 (  0%)             untested:  0 (  0%)
[16:08] <marjo> once the installer is fixed, server results should look even better
[16:08]  * slangasek nods
[16:09] <marjo> Specs status and burn-down chart:
[16:09] <marjo> http://piware.de/workitems/qa/lucid/report.html
[16:09] <marjo> * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:09] <marjo> [cr3] Add DX PPA when testing and reboot if new packages are discovered: INPROGRESS
[16:09] <marjo> * UbuntuSpec:lucid-qa-checkbox-integrate-regression-testing
[16:09] <marjo> No progress since last week.
[16:09] <MootBot> LINK received:  http://piware.de/workitems/qa/lucid/report.html
[16:09] <marjo> * UbuntuSpec:lucid-qa-kernel-test-automation
[16:09] <marjo> [cr3] Merge kernel team test scripts into checkbox: INPROGRESS
[16:09] <marjo> [cr3] Initial daily kernel tests running by Lucid Alpha1: INPROGRESS
[16:09] <marjo> [cr3] The kernel tests (most of them) need sudo: INPROGRESS
[16:09] <marjo> good progress overall on qa blueprints over the past week
[16:09] <marjo> that's all from QA team
[16:10] <slangasek> lucid-qa-kernel-test-automation shows as 18% done; the rest is on track for alpha-2 (just 3 work weeks away)?
[16:11] <marjo> yes
[16:11] <slangasek> ok, great
[16:11] <slangasek> thanks!
[16:11] <slangasek> [TOPIC] Desktop Team
[16:11] <marjo> thank you!
[16:11] <pitti> Usual weekly summary/bug/status page: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:11] <pitti> pretty quiet on the RC bug front
[16:12] <pitti> as for the BPs you called out, quick status update:
[16:12] <pitti> desktop-lucid-une: Didier worked on this, it's 80% now
[16:12] <pitti> desktop-lucid-likewise-open-migration: blocked on upstream sending us the new package (which has been planned for start of January)
[16:12] <pitti> desktop-lucid-empathy-indicator: alpha-2 items are done, the linked bug is not an alpha-2 target (and not milestoned as such) → semantical problem in WI tracker
[16:12] <pitti> desktop-lucid-default-apps: 4 WIs are two MIRs and seeding, the 5th is a package update; should be on track
[16:12] <pitti> so for those I feel that we are on track.
[16:12] <pitti> The only one which is indeed in jeopardy is desktop-lucid-social-from-the-start; I talked to Ken, and he thinks he can get done some stuff over the holidays (quote "I enjoy hacking on gwibber"), so I didn't give up on that one yet
[16:14] <slangasek> ok, cool
[16:14] <Riddell> Kubuntu?
[16:14] <slangasek> there's also a milestoned bug on your list, #494627 - still on track?
[16:14] <slangasek> Riddell: yes please
[16:15] <Riddell> KDE 4.4 beta 2 packaging now in progress
[16:15] <Riddell> 1 MIR outstanding for libssh 492931
[16:15] <Riddell> Updated documentation under way
[16:15] <Riddell> Kubuntu Netbook Preview renamed to Kubuntu Netbook Remix
[16:15] <Riddell> ARM packages nearly all compiled, install images should be buildable later today
[16:15] <Riddell> https://wiki.ubuntu.com/Kubuntu/Todo
[16:15] <ScottK> I'd like to make a plea for priority on Bug #492931 <-- Means no SFTP until KDE can build against it.
[16:15] <ubottu> Launchpad bug 492931 in libssh "MIR for libssh" [Undecided,New] https://launchpad.net/bugs/492931
[16:15] <pitti> slangasek: 494627> need to consult Scott, but I hope it won't be so hard to wait for fsck to finish before starting gdm
[16:15] <Riddell> hint to asac there :)
[16:16] <Keybuk> pitti: patience ;)
[16:16] <slangasek> pitti: different bug, bug #494627 is the nv segfault bug
[16:16] <ubottu> Launchpad bug 494627 in xserver-xorg-video-nv "nv driver crashing with segmentation fault in libpthread.so.0" [High,In progress] https://launchpad.net/bugs/494627
[16:17] <slangasek> I see you have that as "fixed upstream" in your report, so ok :)
[16:17] <pitti> oops
[16:17] <pitti> right, that's easy now
[16:18] <slangasek> bug #492931 is assigned to asac, who is out - can someone else look at it in his stead?
[16:18] <ubottu> Launchpad bug 492931 in libssh "MIR for libssh" [Undecided,New] https://launchpad.net/bugs/492931
[16:18] <Riddell> slangasek: rumour has it asac is still around to look at it
[16:19] <slangasek> ok
[16:19] <slangasek> so no further action there, I guess
[16:19] <slangasek> anything else on desktop?
[16:20] <pitti> not from me
[16:20] <slangasek> moving on
[16:20] <slangasek> [TOPIC] DX Team
[16:20] <njpatel> Weekly summary page: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:20] <njpatel> Lot's of work on appindicator (including initial release), and continued work on UNE UI, otherwise a bit slow, some people on holidays/conferences.
[16:21] <njpatel> alpha2 burndown chart @ http://piware.de/workitems/dx/lucid-alpha2/report.html
[16:21] <slangasek> http://piware.de/workitems/dx/lucid-alpha2/report.html suggests there's significant work yet to be done for alpha-2 - expected to pick up after Jan 1?
[16:21] <MootBot> LINK received:  http://piware.de/workitems/dx/lucid-alpha2/report.html suggests there's significant work yet to be done for alpha-2 - expected to pick up after Jan 1?
[16:21] <njpatel> slangasek: yep, Jan 1 onwards should see quicker progress
[16:22] <slangasek> dx-lucid-xsplash status concerns me, but of course that's blocked on plymouth, which I know is in progress
[16:23] <slangasek> I guess you're ready to hit the ground running when plymouth is in :)
[16:23] <njpatel> That's the plan :)
[16:24] <njpatel> Also, some of the other bits-and-pieces in the blueprints require the foundation work we're doing now with the appindicators/dbusmenu etc
[16:24]  * slangasek nods
[16:24] <slangasek> looks good to me
[16:25] <slangasek> anything else you think we should discuss in more detail, that's in jeopardy for alpha-2?
[16:25]  * njpatel takes another look
[16:26] <njpatel> I don't think so, I can't think of anything that has been raised
[16:26] <tedg> Nothing that we know of.
[16:26] <slangasek> ok
[16:26] <slangasek> [TOPIC] Mobile Team
[16:26] <slangasek> njpatel,tedg: thanks
[16:26] <JamieBennett> asac is on vacation so I'll do my best to summarize
[16:26] <slangasek> JamieBennett: hi
[16:26] <JamieBennett> Weekly summary page: https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:27] <JamieBennett> Good progress on most specs targeted at alpha-2: http://piware.de/workitems/mobile/lucid-alpha2/report.html
[16:27] <JamieBennett> Overall progress is OK: http://piware.de/workitems/mobile/lucid/report.html
[16:27] <JamieBennett> Work items increased this week as we now track a late coming community spec - mobile-lucid-liquid - https://blueprints.edge.launchpad.net/ubuntu/+spec/mobile-lucid-liquid
[16:27] <slangasek> there's a dip in the number of work items targeted to alpha-2 since yesterday; anything we should discuss there?
[16:27] <JamieBennett> Work items decreased as some were moved to alpha-3 but GrueMaster has no alpha-3 work items so no risk
[16:27] <slangasek> ok
[16:28] <JamieBennett> We now have bootable images for dove and iMX51. We had a iMX51 regression but that was fixed
[16:28] <JamieBennett> 2D launcher code is in REVU and dependencies have been sync'ed or MIR'ed. We are unblocked on this one and making good progress
[16:28] <JamieBennett> We don't have a number of how many packages got rebuilt; most porting issues left are about making stuff multi-core save but now we have both images work on this should speed up
[16:28] <JamieBennett> bug 488354 has a PoC fix but we need to work in upstream feedback before landing
[16:28] <ubottu> Launchpad bug 488354 in firefox "NS_InvokeByIndex in xptcinvoke_arm.cpp is not Thumb-2 safe for Lucid" [Unknown,Confirmed] https://launchpad.net/bugs/488354
[16:28] <JamieBennett> and bug 495066 is a desktop bug ;)
[16:28] <ubottu> Launchpad bug 495066 in netbook-launcher "Lucid netbook-launcher segfaults when started" [Critical,Confirmed] https://launchpad.net/bugs/495066
[16:29] <JamieBennett> overall in good shape
[16:30] <slangasek> "don't have a number of how many packages got rebuilt" - that's due at alpha-2, correct?
[16:30] <JamieBennett> now we have the two images that can be determined for alpha-2 when we review
[16:30] <JamieBennett> so yes
[16:31] <mdz> 495066 is marked critical, milestoned for alpha 2, but has no one assigned
[16:31] <mdz> and I don't think it was mentioned in the desktop team's update
[16:31] <slangasek> "images" - I thought this is supposed to be a rebuild of all of main, not just what's on the images
[16:32] <JamieBennett> asac can give more details of the review but I think is all of main
[16:32] <slangasek> right, so we can't rely on the images being a reference point
[16:32] <JamieBennett> right
[16:32] <slangasek> should we discuss out of band what the plan is for getting the list of packages that haven't been rebuilt?
[16:33] <JamieBennett> slangasek: ping asac when he is back from vacation
[16:33] <JamieBennett> or if you can catch him earlier
[16:33] <slangasek> [ACTION] slangasek to confirm with asac how to get the list of packages that still need rebuilt for arm toolchain
[16:33] <JamieBennett> maybe pitti can comment on bug 495066 ?
[16:33] <ubottu> Launchpad bug 495066 in netbook-launcher "Lucid netbook-launcher segfaults when started" [Critical,Confirmed] https://launchpad.net/bugs/495066
[16:34] <slangasek> pitti: are you aware of bug #495066, since JamieBennett says it's a desktop bug?
[16:34] <pitti> JamieBennett: first time I saw it, TBH; I assigned it to didrocks now
[16:34] <JamieBennett> OK
[16:34] <pitti> help from mobile team is appreaciated, of course
[16:34] <JamieBennett> :)
[16:35] <pitti> (since Didier doesn't start until January 11)
[16:35] <ttx> french slackers...
[16:35]  * pitti puts on desktop release page
[16:35] <mdz> pitti: should there be a desktop team bug contact etc. on netbook-launcher?
[16:35] <JamieBennett> maybe StevenK can take a look at that bug, I'll ping him later
[16:35] <mdz> or whatever you use for getting notified of bugs?
[16:36] <pitti> mdz: right, once we actually have someone (didrocks) to work on those
[16:36] <slangasek> JamieBennett: I also had 458501 on my radar, it's listed as "needs debugging" in your report - is help needed there?
[16:36] <mdz> njpatel might know something about 495066 as well
[16:37] <JamieBennett> slangasek: Not sure on whats holding that up, I can check
[16:37] <slangasek> please do (out of band)
[16:37] <njpatel> I had a look earlier today, seems we're sending a NULL pointer where it isn't appreciated...I'll have a closer look and try to make a patch
[16:38] <slangasek> njpatel: great, thanks!
[16:38] <pitti> njpatel: cheers
[16:38] <slangasek> any other concerns on the Mobile front?
[16:38] <JamieBennett> not from me
[16:39] <slangasek> hmm, https://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-arm-lightweightbrowser says "make firefox use lucid default toolchain flags" is still outstanding... any idea how that's going?
[16:40] <JamieBennett> slangasek: firefox 3.6 has all the bits so once we get that we have it
[16:40] <slangasek> ok
[16:40] <slangasek> [TOPIC] Server Team
[16:40] <slangasek> JamieBennett: thanks
[16:40] <slangasek> ttx: hello
[16:40] <ttx> hello everybody
[16:40] <ttx> status updated at: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:41] <ttx> for the specs you mention:
[16:41] <ttx> server-lucid-landscape-refresh: All work items completed
[16:41] <ttx> server-lucid-seeds: Discussion is long, but  implementation should be short
[16:42] <ttx> server-lucid-euca-remote-autoregister: Delayed by 1.6.2 integration work, should be on track next week
[16:42] <ttx> server-lucid-eucalyptus-karmic-retrospective: 75% completed, on track
[16:42] <ttx> server-lucid-eucalyptus-merging-and-packaging: 76% completed, 1.6.2 should land once the MIR bugs are processed
[16:42] <ttx> hm, make that 79% now
[16:42] <ttx> server-lucid-canonical-application-support: 74% completed, on track
[16:43] <ttx> server-lucid-uec-testing: Just getting started, Mathias just got back from vacation
[16:43] <ttx> server-lucid-ec2-boothooks: Just getting started, Scott was working on his other alpha2 specs
[16:43] <jiboumans> (pending MIR reviews for server-lucid-canonical-application-support)
[16:43]  * pitti makes a mental note to round completion to 5% steps
[16:43] <ttx> same for server-lucid-ec2-config
[16:43] <slangasek> pitti: noooo :)
[16:44] <slangasek> jiboumans: are there MIR reviews pending there other than the two that have been targeted and milestoned to alpha-2?
[16:44] <ttx> For the two MIR bugs targeted to alpha2, I enabled the test suites and uploaded a new version for them
[16:44] <ttx> that was the only MIR blocker
[16:44] <slangasek> (bug #497390, bug #497455)
[16:44] <ubottu> Launchpad bug 497390 in libproxool-java "MIR for libproxool-java (and avalon-framework)" [High,Fix committed] https://launchpad.net/bugs/497390
[16:44] <ubottu> Launchpad bug 497455 in libwoodstox-java "MIR for libwoodstox-java" [High,Fix committed] https://launchpad.net/bugs/497455
[16:44] <ttx> so they should be good to process now
[16:44] <ttx> ..or processed
[16:44] <jiboumans> slangasek: yes, there are a few listed in https://blueprints.edge.launchpad.net/ubuntu/+spec/server-lucid-canonical-application-support
[16:45] <pitti> ttx: note that approved MIRs will stay in that state until something actually pulls them into main
[16:45] <slangasek> great; sounds like there are good explanations for those alpha-2 specs that still have a way to go to completion
[16:45] <pitti> ttx: i. e. we won't move stuff to main just because it has an approved MIR
[16:45] <ttx> slangasek: and our burndown charts look good
[16:45] <mdz> pitti: in this case I believe 1.6.2 (already uploaded) depends on them
[16:45] <ttx> pitti: something does
[16:45] <mdz> (eucalyptus 1.6.2)
[16:45] <pitti> slangasek: precision> you want three digits after the comma instead? :-)
[16:46] <pitti> ttx: great (just wanted to mention, to avoid a deadlock)
[16:46] <ttx> pitti, mdz: euca 1.6.2 depends on euca-commons-ext 0.5.0 which depends on proxool
[16:46] <ttx> and euca 1.6.2 runtime depends on woodstox
[16:46] <slangasek> ttx: yes; I wanted to double-check that the burndown chart wasn't masking, e.g., all the outstanding items being on one spec that wasn't going to get done in time
[16:46] <ttx> pitti: do I need to retry the builds ?
[16:46] <mdz> is there any way we could get eucalyptus 1.6.2 accepted today?
[16:47] <mdz> so that it's ready for ISO testing on Monday?
[16:47] <pitti> ttx: no, they'll build automatically as long as they are in depwait
[16:47] <slangasek> ttx: can you take an action to target all the canonical-application-support MIRs to lucid, and milestone to alpha-2 (if appropriate)?
[16:47] <ttx> slangasek: sure
[16:47] <jiboumans> ttx: for reference taht should be on zul's plate
[16:47] <slangasek> [ACTION] ttx, zul to target all the canonical-application-support MIRs to lucid, and milestone to alpha-2
[16:48] <ttx> mdz: should be done automatically, if pitti is right (and he always is) :)
[16:48] <ttx> mdz: i'll keep an eye on it this weekend
[16:48] <mdz> ttx: no, those packages must be manually moved from universe to main first
[16:48] <slangasek> ttx: and fyi, if you add the MIR bugs to the blueprint using 'link a bug report', you don't have to update their status by hand ;)
[16:48] <slangasek> (update the work item status)
[16:49] <mdz> given the MIRs are approved, I'm wondering if we can get the archive changes done to unblock it
[16:49] <slangasek> mdz: I can take care of that today
[16:49] <pitti> ttx: (promoted)
[16:49] <slangasek> ... or pitti can
[16:49] <mdz> slangasek: ...assuming pitti hasn't already done it ;-)
[16:49] <ttx> pitti: cool, thanks
[16:49] <slangasek> :)
[16:49] <mdz> pitti: thank you
[16:50] <slangasek> anything else on server?
[16:50] <slangasek> [TOPIC] Kernel Team
[16:50] <slangasek> ttx, jiboumans: thanks
[16:50] <slangasek> pgraner, apw: hi
[16:51] <apw> Overall Kernel Team status is summarised at the URL below, including the items called out in the agenda.  The AppArmour update has now hit the archive closing out our alpha-1 deliverables.
[16:51] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:51] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:51] <apw> So far our main alpha-2 deliverables are on track, Alpha-2 status is at the URL below.  Of note ATI Radeon KMS is enabled in the kernels in the archive, we are waiting on userspace to catch up.  Also we are progressing well on the overall boot time budget, currently hovering right around 2s, spot on our budget.
[16:51] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[16:51] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[16:51] <apw> We are starting to see some bugs reported by testers and are trying to stay on top of those as well.
[16:52] <apw> ..
[16:53] <slangasek> I'm excited to see that the kernel is already hitting its boot budget
[16:53] <apw> qudos to Keybuk for all his udev jiggery-pokery to get us to where we are today in initramfs
[16:53] <slangasek> now, can we hold it there for 4 months :)
[16:54] <apw> now its visible, we can try very hard!
[16:54] <Keybuk> slangasek: did you look at 20091218.1 ? :-)
[16:54] <Keybuk> the kernel has smashed its budget
[16:54] <apw> shhhh, thats next weeks "hoorah"
[16:55] <apw> nothing else from me
[16:55] <slangasek> apw: kernel-lucid-suspend-resume is marked essential for alpha-2, but you say it's "not release critical" in your report; update the spec priority, then?
[16:55] <slangasek> Keybuk: sweeeet
[16:55] <apw> slangasek, hrm so it is ... thanks
[16:55] <slangasek> thank you!
[16:55] <slangasek> anything else on kernel?
[16:56] <pgraner> apw: manjo has been on holiday, he was supposed to fix it up
[16:56] <pgraner> apw: just touch it up for him pls
[16:56] <apw> done
[16:58] <slangasek> [TOPIC] Security Team
[16:58] <slangasek> apw, pgraner: thanks again
[16:58] <jdstrand> o/
[16:58] <slangasek> jdstrand: hi
[16:58] <jdstrand> so, as before, status is tracked here: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[16:59] <jdstrand> our essential bps are all still on track, and there is nothing surprising that came up this week
[16:59] <jdstrand> other than what can be seen in the report, there isn't much more to add
[17:00] <slangasek> jdstrand: you guys don't have anything targeted to alpha-2, but http://piware.de/workitems/security/lucid shows you a bit above the target line; is it time to start reviewing and deferring some of this?
[17:00] <jdstrand> slangasek: we don't track for alpha-2
[17:01] <jdstrand> all our stuff is for release, since we are very interrupt driven
[17:01] <kees> ^ not
[17:01] <kees> also, 1/3rd of our team is on vacation at the moment.
[17:01] <slangasek> jdstrand: yes, I mean you're above the target line for the release as a whole; if a lot of these specs are informational / documentation then that's not a concern, but if these are archive changes, we don't want them all landing Mar 31 :)
[17:02] <jdstrand> slangasek: the problem is that we are committed to essential bps
[17:02] <jdstrand> slangasek: the burndown shows everything from low to essential
[17:02] <jdstrand> we are committed to achieving our essential items, but not high and lower
[17:03] <slangasek> yes, I'm suggesting that in the next month or so, it would probably be a good idea to review some of the lower-priority specs and explicitly deferring them
[17:03] <slangasek> -ring
[17:03] <jdstrand> we will of course work towards them, but the workitems tracker is an imperfect fit for our team atm
[17:03] <slangasek> alright
[17:04] <jdstrand> it was discussed with robbiew that it is not expected that our burndown be below the line
[17:04] <slangasek> nothing else from me on security; anyone else?
[17:04] <slangasek> jdstrand: fair enough
[17:04] <jdstrand> in terms of deferring stuff, we will of course be looking at it, but it might not make sense to defer too soon
[17:04] <jdstrand> (we could still make it later in the cycle...)
[17:05] <slangasek> jdstrand: is the tool useful to your team, in that case?  if you guys aren't using it at all, maybe it's better to not have that report :)  (but robbiew may disagree)
[17:05] <jdstrand> slangasek: the tool is useful, yes
[17:05] <slangasek> ok
[17:05] <slangasek> [TOPIC] Foundations team
[17:05] <slangasek> jdstrand, kees: thanks :)
[17:06] <jdstrand> slangasek: the burdown chart could use some filtering, but even then, we might not always be below the line (since dev work is secondary)
[17:06] <slangasek> Keybuk: are you standing in for Foundations, or just kiboing the highlights?
[17:06] <slangasek> jdstrand: yep, understood
[17:07] <Keybuk> I'm not aware of standing in ;)
[17:07] <slangasek> heh
[17:08] <ScottK> You are now
[17:08] <slangasek> https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:08] <slangasek> hasn't been updated for two weeks, but the burndown chart is still accurate :)
[17:08] <slangasek> http://piware.de/workitems/foundations/lucid-alpha2/report.html
[17:08] <MootBot> LINK received:  http://piware.de/workitems/foundations/lucid-alpha2/report.html
[17:09] <slangasek> half those "TODO" items are in progress on Keybuk's plate, so no problems there
[17:10] <Keybuk> right
[17:10] <Keybuk> they're all "committed"
[17:10] <ScottK> I'd like to make a plea for foundations support on qt4-x11 on powerpc.  It fails do to ld segfaulting which is well beyond my capabilities (particularly since I have no hardware)
[17:10] <Keybuk> pending upload of new mountall, and integrating plymouth into the boot
[17:10] <Keybuk> which I'm holding back a little on to get performance going in the right direction
[17:10] <slangasek> the gfxboot update still has a bit of work outstanding; will check with cjwatson on that, when he's not on vac
[17:11] <slangasek> Keybuk: ok.  Aside from performance, are the bits in ubuntu-boot ppa solid enough that early adopters should consider grabbing?
[17:11] <slangasek> ScottK: is there a bug number currently?
[17:11] <Keybuk> slangasek: err
[17:11] <Keybuk> only if they know how to boot their machine when things go wrong ;p
[17:11] <ScottK> I don't think so, but I'll check.
[17:12] <slangasek> Keybuk: by "early adopters" I mean "me" ;)
[17:12] <Keybuk> if you like
[17:12] <slangasek> [ACTION] slangasek to check on ld segfault on powerpc building qt4-x11
[17:12] <Keybuk> but again, don't cry to me when it doesn't work :p
[17:12] <slangasek> heh
[17:12] <Keybuk> because I'll be too busy crying myself
[17:12] <slangasek> Keybuk: that's ok, I was going to cry to you about bootchart spitting out 1.5GB of data and filling my /var/run tmpfs instea
[17:12] <slangasek> d
[17:13] <slangasek> :-)
[17:13] <slangasek> anyone else have any questions/concerns on foundation?
[17:13] <slangasek> +s
[17:13] <Keybuk> slangasek: if it does that, that's a sign of a bigger boot problem
[17:13] <Keybuk> that implies your rcS and rc2 haven't been run <g>
[17:13] <slangasek> [TOPIC] MOTU
[17:14] <slangasek> Keybuk: 'runlevel' confirms, hmm :)
[17:14] <ScottK> Nothing major on MOTU.
[17:14] <ScottK> The only issue I'm working currently is the one we already talked about.
[17:14]  * slangasek nods
[17:14] <slangasek> no big transitions on the radar yet?
[17:14] <ScottK> Not a lot of action on new packages, so if people want to look at REVU, plenty to review
[17:15] <ScottK> slangasek: I'm not even going to look at it until after DIF.
[17:15] <slangasek> fair 'nuff
[17:15] <Keybuk> slangasek: of course, that really proves how pointless the stuff left in those is, but hey :p
[17:16] <slangasek> any other questions on MOTU?
[17:16] <slangasek> #endmeeting
[17:16] <slangasek> #end, #end, damn meeting
[17:16] <slangasek> thanks, all :)
[17:16] <slangasek> Keybuk: actually, everything /in/ rc2 appears to be running
[17:16] <ScottK> slangasek: I looked at binutils and I don't see anything obviously related to qt4-x11 on powerpc
[17:16] <apw> slangasek, thanks
[17:17] <pitti> thanks al
[17:17] <pitti> l
[17:17] <slangasek> ScottK: ack; will pursue it from the bug log
[17:17] <Keybuk> slangasek: is one of your network-interface jobs stuck at start/starting ?
[17:17] <ScottK> slangasek: Thanks.
[17:18] <slangasek> Keybuk: no (--> #ubuntu-devel?)
[17:18] <Keybuk> oh, that's the usual failure case
=== fader_ is now known as fader|lunch
=== fader|lunch is now known as fader_
=== yofel_ is now known as yofel
=== FFEMTcJ|mobile_ is now known as FFEMTcJ|mobile
=== asac_ is now known as asac
=== fader_ is now known as fader|away
=== FFEMTcJ|mobile_ is now known as FFEMTcJ|mobile
=== geirha_ is now known as geirha
=== asac_ is now known as asac
=== elky is now known as elky`
=== elky` is now known as elky
=== maco_ is now known as maco2