[15:59]  * marjo waves
[15:59]  * Riddell high fives
[15:59] <pitti> hello
[16:00] <ttx> o/
[16:00] <davidbarth> o/
[16:00] <asac> o/
[16:01] <jiboumans> o/
[16:03]  * apw fades gently in from the background
[16:05]  * ttx executes a quick dance to entertain the audience while waiting
[16:05]  * Riddell nudges slangasek 
[16:08] <Riddell> anyone want to phone him?
[16:09] <slangasek> he
[16:09] <slangasek> sorry
[16:09] <slangasek> s/he/hi/
[16:09] <slangasek> #startmeeting
[16:09] <MootBot> Meeting started at 10:09. The chair is slangasek.
[16:09] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:10] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-19
[16:10] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-19
[16:10] <slangasek> [TOPIC] QA Team
[16:10] <MootBot> New Topic:  QA Team
[16:10] <slangasek> marjo: hi
[16:10] <marjo> slangasek: hi
[16:10] <marjo>    * Hardware testing
[16:10] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:10] <marjo> Netbook:
[16:10] <marjo>    passed:   9 (70%)   failed:   2 (15%)   untested: 2 (15%)
[16:10] <marjo> Laptop:
[16:10] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:10] <marjo>    passed:   25 (96%)   failed:    1 ( 4%)   untested:  0 ( 0%)
[16:10] <marjo> Server:
[16:10] <marjo>    passed:   52 (98%)   failed:    0 ( 0%)   untested:  1 ( 2%)
[16:10] <marjo> Desktop:
[16:11] <marjo>    passed:   11 (92%)   failed:    0 ( 0%)   untested:  1 ( 8%)
[16:11] <marjo> Bug 499940 remains open and detected in certification:
[16:11] <marjo> 499940 - [lucid regression] does not resume from hibernation, restarts
[16:11] <marjo> fresh (Confirmed, High)
[16:11] <marjo> slangasek: would like your help nudging 499940 along
[16:11] <marjo> seems got unassigned from kernel
[16:11] <apw> marjo, unassigned from canonical-ekernel-team ?  that would be normal
[16:12] <marjo> apw: don't know next steps
[16:12] <marjo> any suggestions?
[16:13] <apw> the suspicion seems to be there is things are going wrong in userspace cause it is finding two matches for the disk
[16:13] <apw> i've not looked any closer ... who knows that side of things
[16:13] <slangasek> I can look into this on the cryptsetup side
[16:13] <apw> slangasek, perhaps you an i can coordinate on this one
[16:14] <slangasek> (not for a3; beta-1 seems like the realistic milestone there still)
[16:14] <marjo> slangasek, apw: much appreciated
[16:14] <slangasek> (assigned myself)
[16:14] <marjo> thx gentlemen!
[16:14] <marjo>    * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:14] <marjo> Desktop Experience Team PPA has been enabled across HW Cert. satellite
[16:14] <marjo> servers in order to test packages. Attachment has been added to the
[16:14] <marjo> checkbox-certification package in order to gather information returned from
[16:14] <marjo> dbusmenu-bench to create metrics across certification hardware.
[16:14] <marjo> Still targeting for lucid-alpha-3.
[16:14] <marjo>    * UbuntuSpec:qa-lucid-automated-server-testing
[16:14] <marjo> Alpha 3 work items are at risk, sbeattie working to resolve test
[16:14] <marjo> integration blockers
[16:15] <marjo> that's it from QA team
[16:15] <marjo> any questions?
[16:16] <slangasek> marjo: lucid-qa-checkbox-desktop-experience-tests shows as 0 of 4 workitems completed; is this still on track for a3?
[16:16] <marjo> yes, see above notes
[16:16] <marjo> re progress made overnight
[16:17] <slangasek> ok
[16:17] <marjo> after consulting w/ cr3, will change wording of work items, if appropriate
[16:18] <slangasek> no other questions from me; anyone else?
[16:18] <marjo> slangasek: thx!
[16:18] <davidbarth> marjo: i think we only need a hook to get packages out of our ppa in the test images and then a hook to trigger a test script within the packages
[16:18] <marjo> davidbarth: ack
[16:19] <marjo> that would be sufficient integration, i think
[16:19] <marjo> will work w/ cr3 on finishing up
[16:19] <marjo> w/ your team's feedback
[16:19] <davidbarth> ok
[16:19] <marjo> thx davidbarth
[16:20] <slangasek> [TOPIC] Server Team
[16:20] <MootBot> New Topic:  Server Team
[16:20] <slangasek> marjo: thanks
[16:20] <ttx> o/
[16:20] <slangasek> ttx: hi
[16:20] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:21] <ttx> Server Alpha3/Milestoned Bugs:
[16:21] <ttx> bug 524258: cloud-init update check code is not enabled (smoser)
[16:21] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:21] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:21] <ttx> This is ready, pending some cloud-init upload
[16:21] <ttx> (more on this later)
[16:21] <ttx> High/Essential specs at < 90% completion:
[16:22] <ttx> server-lucid-mysql-5.0 (80%): All work committed, only one test work item left
[16:22] <ttx> server-lucid-uec-testing (82%): Last work items are about testing Alpha3 candidates next week
[16:22] <ttx> server-lucid-seeds (80%): Last work item about CTDB MIR, will be dropped if it cannot meet requirements
[16:22] <ttx> Bugs affecting server, in other teams:
[16:22] <ttx> Only one blocking a3 spec delivery:
[16:23] <ttx> bug 524484: upstart fails to build (fixes needed for earlier boothooks)
[16:23] <ttx> contains fix for bug 504883
[16:23]  * slangasek nods
[16:23] <ttx> I think it's pretty straightforward :)
[16:23] <ttx> Other b ugs:
[16:23] <ttx> bug 506297: Graphical Ubuntu logo enabled on servers, no more login prompt
[16:24] <ttx> and the recent bug 524439
[16:24] <ttx> the combination of both would make the milestone look nasty :)
[16:24] <slangasek> I can upload 524484 today, rather than waiting for Keybuk to be around again Monday
[16:24] <ttx> slangasek: great, thanks
[16:25] <ttx> all bugs targeted to Lucid and milestones to a3
[16:25] <ttx> We expect to file a few FeatureFreeze exceptions:
[16:25] <ttx> cloud-init: runcmd feature enabled in cloud-config + possibly moving earlier in the boot sequence, after bug 524484 is fixed
[16:25] <slangasek> console-setup> am going to assign that one to Keybuk, it's probably fallout from the plymouthification change
[16:25] <ttx> slangasek: yes
[16:26] <ttx> that's th only one affecting High specs ^
[16:26] <slangasek> (and even if I could get to it today, I doubt I'd make any headway)
[16:26] <ttx> the other two are for Low specs:
[16:26] <ttx> vmbuilder: soren is still working on a few new features, should file FFe on Monday
[16:26] <ttx> cloud-utils: add euca-run-instances-and-[wait|connect] utility
[16:26] <ttx> that last one is mostly harmful, but you decide.
[16:27] <ttx> We don't expect anything else
[16:27] <ttx> fresh cloud-init ffe request: bug 524516
[16:27] <ttx> (that's just-in-time reporting)
[16:27] <ttx> All for me, questions ?
[16:28] <slangasek> a little too fresh, ubuntu-release hasn't been subscribed to it :)
[16:28] <ttx> ah
[16:28] <ttx> let me parallelize
[16:29] <slangasek> no questions here; anyone else?
[16:29] <ttx> slangasek: moving the boot hook earlier in the boot process is the most disruptive "feature"
[16:29]  * slangasek nods
[16:29] <ttx> slangasek: could be considered a bug depending on how you look at it
[16:29] <ttx> We want to land it today rather than next week, if possible
[16:29] <ttx> so that we have plenty of time to revert it if it proves unstable for any reason
[16:30] <slangasek> yes, so I'll get upstart fixed so that's possible, but then we still have the "ssh not running" issue that didn't shake out at the sprint
[16:30] <smoser> slangasek, i have that resolved.
[16:30] <slangasek> smoser: oh, great
[16:30] <smoser> the other cloud-init jobs were blocking boot due to imposible 'start on (a nd b)' combinations.
[16:31] <slangasek> ah
[16:31] <slangasek> [TOPIC] Mobile Team
[16:31] <MootBot> New Topic:  Mobile Team
[16:31] <slangasek> ttx, smoser: thanks
[16:31] <slangasek> asac: hi
[16:31] <asac> hi
[16:31] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid#preview
[16:31] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid#preview
[16:31] <asac> damn preview ;)
[16:32] <asac> so we were able to verify that our X0 dove boards are good
[16:32] <asac> still testing, bceause we had a kernel issue half of the week
[16:32] <asac> i also added "firefox yahoo rollout" to the summary, because that occupied me quite some time this week
[16:33] <asac> on work items:
[16:33] <slangasek> asac: is that bug #522834?
[16:33] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:33] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:33] <asac> slangasek: ack thanks.
[16:33] <slangasek> (ah, bug closed since last night, ok)
[16:34] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html
[16:34] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html
[16:34] <asac> i tried to postpone most stuff that wasnt done today ... will review another time after the meeting
[16:34] <asac> so probably important for this meeting the potential post a3 items
[16:34] <asac> * mobile-lucid-arm-gcc-v7-thumb2: green light for rebuild after a3
[16:34] <asac> * mobile-lucid-arm-lightweightbrowser: security team decision pending
[16:35] <asac> -> this one is most likely a no
[16:35] <asac> security team and me agree mostly that it would be better not pushed into lucid+1
[16:35] <asac> there might be push back from other stakeholders though ... so lets cross fingers
[16:35] <asac> (chromium)
[16:36] <slangasek> when do you expect that security team decision?
[16:36] <asac> the other two blueprints we still would really like to see getting done are the webservice specs
[16:36] <jdstrand> slangasek: we'll likely review it today
[16:36] <asac> slangasek: once kees is up ... i want him to give his NO on the MIR bug
[16:36] <slangasek> ok
[16:36] <asac> or YES fwiw ;)
[16:37] <asac> slangasek: the webservice specs are definitly none-intrusive. my internel almost-hard deadline for the implementation is end of next week. if we dont have that by then, we will develop it outside of the archive most likely
[16:38] <asac> point is that without them we wont have office on arm and email is really just a mailto: handler that parses the mailto: url and opens the proper webmail url based on the users choice of webmail provider
[16:38] <asac> slangasek: of course we would file FFe bugs once we know that those happen
[16:38] <asac> or do you want that bug up-front?
[16:39] <slangasek> those are the medium-priority specs mobile-lucid-arm-webservice-for-{email,office} +
[16:39] <slangasek> ?
[16:39] <asac> yes
[16:39] <slangasek> if you don't know yet whether you want it in the archive, no need to file the FFe yet
[16:40] <asac> slangasek: right. how much delay would release team be ok to accept? i guess you need to see the code first?
[16:40] <slangasek> not necessarily
[16:40] <pitti> for the web services links?
[16:40] <asac> pitti: its not links only
[16:40] <asac> pitti: its a mailto: handler for email that does some nice stuff
[16:40] <slangasek> most FFes are done based on a description of what's being uploaded, not the code
[16:41] <asac> and for office its an auto import/view on the web
[16:41] <pitti> well, I guess there's some .desktop file and some glue code around it
[16:41] <ogra> mime types too very likely
[16:41] <asac> more or less yes, pitti
[16:42] <asac> right. i consider mime-types to be part of auto import/view ...
[16:42] <asac> anyway, i will file the bugs with info we have now
[16:42] <asac> thats it from our side.
[16:42] <asac> questions
[16:42] <asac> ?
[16:42] <slangasek> asac: the number of thumb2 FTBFS bugs targeted at a3 has gone down some since this morning, but not much; are these others still in progress, or are they going to need deferred to beta-1?
[16:42] <slangasek> and does the slow progress here mean more resources need to be thrown at them?
[16:42] <asac> slangasek: i will push them to beta-1 ... and if we get fixes before a3, just upload (if its before the freeze)
[16:42] <ogra> i think thats a constant task
[16:42] <asac> slangasek: the list is quite short. we should be fine
[16:43] <slangasek> ok
[16:43] <asac> slangasek: problem is that this week half of the team was travelling for two days ;)
[16:43] <slangasek> ah
[16:43] <asac> slangasek: i will just retarget them. those are just bugs that need to get fixed for release
[16:43] <slangasek> any other questions for Mobile?
[16:43] <asac> of course the sooner the better
[16:43] <asac> (thats why i used the early a3 target initially)
[16:44] <slangasek> [TOPIC] Kernel Team
[16:44] <MootBot> New Topic:  Kernel Team
[16:44] <asac> thanks
[16:44] <slangasek> asac: thanks
[16:44] <ogra> thanks
[16:44] <slangasek> apw: hi
[16:44] <apw> hi
[16:44] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Alpha-3 activity is summarised at the second URL below, of which we have completed approximatly 65%.  We remain above the line on our burn-down chart (at the third URL below), but are still making progress.
[16:44] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:44] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:44] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:44] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:44] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:44] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:44] <apw> We have suspend/resume testing going on this week at SCALE.  The ubuntu delta tasks are close to complete with the final driver being dropped.  AppArmour has just been updated again and almost all tasks there are complete.  On boot performance we are within budget and the 5s usb-id bug is now fixed.  Of the ARM bugs picked out one is closed, one should be fixed awaiting feedback, one we have patches, and last is under investigations.
[16:45] <apw> We thought we had uploaded the last kernel for the Alpha-3 freeze, but it seems toolchains have just been uploaded so there will have to be a rebuild there.  Otherwise we have a reasonable kernel ready for Alpha-3.  Marvell Dove has been brought up to the same level and tested to boot with the hardware we have.  Freescale IMX51 also has been tested, and is unlikely to change before Alpha-3.
[16:45] <apw> We have had a lot of discussions this week about the quality of the DRM stack particularly with respect to ATI KMS.  Upstream is basically calling 2.6.32 unmaintainable for DRM.  The upstream position is that we should be takeing a complete DRM backport; and is suggesting that other distros are already doing this.  We are investigating the options here.
[16:45] <apw> ... done
[16:46] <slangasek> hmm, HTTP 500 from wiki.ubuntu.com
[16:46] <slangasek> ah, cleared up
[16:46] <pitti> just got it as well, but works agian
[16:46] <apw> was going to say looks ok here ...
[16:48] <slangasek> apw: these other three kernel bugs are all still targeted to alpha-3; are any of these going to be included in the toolchain rebuild upload?
[16:48] <apw> slangasek, the arm ones you pulled out.  they arn't with the distro kernel anyhow
[16:49] <apw> i'll find out monday i suspect as its 'christmas' in .cn this week
[16:49] <persia> New Years.
[16:49] <apw> i beleieve we have bootable kernels for them all right now, the other fixes may have to wait till right after the un-freeze
[16:49] <slangasek> "aren't with the distro kernel" - not sure what that means?  they're open tasks on the kernel packages
[16:50] <apw> ahh miss thinking there, of course i need to upload them alll cause of GCC ... recompile tastic
[16:51] <apw> i will try and get any that are ready in, due to the time it takes we may not get them in time and get a build in before tuesday end
[16:51] <slangasek> ok; you'll retarget those that don't get included?
[16:51] <apw> ack
[16:54] <slangasek> apw: kernel-lucid-boot-performance only has one outstanding workitem for alpha-3, but it's a doozy - is that still on your radar for the coming week?
[16:54] <slangasek> (investigate readahead by inode number)
[16:54] <apw> yeah thats on my adgenda for next week
[16:55] <slangasek> ok
[16:55] <apw> i have a re-sync with all the 'investigate' type items planned for next monday
[16:55] <slangasek> no other questions here; anyone else?
[16:56] <slangasek> [TOPIC] Desktop Team
[16:56] <MootBot> New Topic:  Desktop Team
[16:56] <slangasek> apw: thanks
[16:56] <slangasek> pitti: hi
[16:56] <pitti> o/
[16:56] <pitti> Spec/bug status: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:56] <pitti> By and large we are done with our alpha-3 work items. Except for desktop-lucid-social-from-the-start, which still needs some packaging changes, MIR, and seeding (all in progress); some bits got postponed, like the new plymouth artwork freeze (which has time until UIF), and some X.org bug harvesting scripts (which are not bound by the release cycle, and just became victim of higher urgency tasks)
[16:56] <pitti> The most "interesting" issue that we have right now is bug 507148.
[16:56] <pitti> This was discussed quite extensively in #u-devel earlier today, and right now it looks like we'll need to backport the linux 2.6.33 drm to our kernel (same like Fedora); it seems drm in 2.6.32 is pretty much doomed, buggy, and unsupported. apw kindly agreed to checking feasibility.
[16:56] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:56] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:56] <pitti> hm, of course apw beat me to this report-wise
[16:57] <pitti> Specs called out in release team meeting invitation:
[16:57] <pitti> - desktop-lucid-default-apps: Remaining WI is a new feature in F-Spot which was just applied to the 0.7 branch; it does not have a release yet, and it's not clear whether it'll be stable by beta-1. Ken now worked on a backport and has a first version available in a PPA; did not make it into alpha-3, but believed to be fixable for beta.
[16:57] <pitti> - desktop-lucid-new-firefox-support-model: The alpha-3 tasks of this spec are all done; there is one extra (localize the Yahoo search engine start page) which is all done in langpack-o-matic, and just waiting for the new langpack export to happen over this weekend.
[16:58] <Riddell> Kubuntu?
[16:58] <Riddell>  * generally in a good position for feature freeze
[16:58] <Riddell>  * Qt 4.6.2 still not packaged, waiting on patch from upstream
[16:58] <Riddell>  * KOffice 2 also still due, packaging is progressing
[16:58] <Riddell>  * Mozilla approved the KDE integration patches to firefox yesterday, asac reviewing for inclusion
[16:58] <Riddell>  * Kubuntu Netbook Remix now in a working state for Lucid
[16:58] <Riddell>  * kdebindings not compiling on ARM (the important bits do compile so we can just work around the unimportant bits)
[16:58] <slangasek> pitti: AIUI, the plymouth theme change involves much more than just artwork; I don't think UIF is the right target there
[16:58] <Riddell>  * main blocker for alpha 3 is installer currently broken, I think it's cross desktop bug 523648
[16:58] <Riddell>  * AMD64 CD still not over mysql breakage but should now be fixed and tomorrow's CD should not be oversized
[16:58] <Riddell>  * https://wiki.ubuntu.com/Kubuntu/Todo
[17:00] <pitti> ah, speaking of which, I got the desktop CDs to build finally, but they are still oversized despite some langpack chopping
[17:00] <pitti> FF was quite a hit apparently
[17:00] <pitti> I'll still work on that
[17:01] <slangasek> pitti: ok; feel free to hand off to me any remaining items that need investigating for CD size at EOD today
[17:01] <pitti> questions anyone?
[17:02] <pitti> slangasek: I'd like to compare alpha-2 CDs to the current ones, to see what sticks out
[17:02]  * slangasek nods
 apparently then
[17:03] <slangasek> yep, no more questions here - thanks!
[17:03] <slangasek> [TOPIC] DX Team
[17:03] <MootBot> New Topic:  DX Team
[17:03] <davidbarth> hi
[17:03] <slangasek> davidbarth: hi
[17:03] <davidbarth> so, relase status as usual at: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:03] <davidbarth> we've landed modules destined for alpha-3 yesterday
[17:04] <davidbarth> details at: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidWeeklyReleases
[17:04] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:04] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:04] <davidbarth> generally quite a lot of new packages, and the end of the dbusmenu/indicate infrastructure
[17:04] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidWeeklyReleases
[17:04] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidWeeklyReleases
[17:05] <davidbarth> now we have even more dynamic menus, to finish the messaging indicator!
[17:05] <davidbarth> ie, apps can register desktop actions in their desktop files, and override that at runtime with other particular action items
[17:05] <slangasek> davidbarth: dx-lucid-gtk-improvements seems to say the changes still need to be integrated in the package; I agree this should be done for alpha-3 - is this on-track?
[17:06] <davidbarth> apart from that excitment...
[17:06] <slangasek> "for alpha-3" -> "ASAP, now that we're past feature freeze"
[17:06] <davidbarth> cs-deco is in gtk as of yesterday evening
[17:06] <slangasek> so that workitem status should be updated?
[17:06] <davidbarth> so that has landed already
[17:06] <slangasek> ok
[17:06] <davidbarth> yes
[17:07] <davidbarth> seb128 created a special gtk-csd tag to track issues created by that gtk patch
[17:07] <davidbarth> (can't find the bug link, but there are a few that are being worked on right now)
[17:08] <davidbarth> dx-lucid-xsplash
[17:08] <davidbarth> no progresses on the x11-plugin (xsplash replacement); postponed to beta-1
[17:08] <davidbarth> so we're late on this one
[17:08] <davidbarth> ie the move to xsplash being an x11 plugin of plymouth
[17:09] <slangasek> https://blueprints.launchpad.net/ubuntu/+spec/dx-lucid-xsplash doesn't reflect that this has been postponed, AFAICS
[17:09] <slangasek> (marked as "INPROGRESS")
[17:09] <davidbarth> right, need to update that too; cody has that back on his plate next week, but we prefered to focus on gtk
[17:10]  * slangasek nods
[17:10] <davidbarth> gtk being "roughly behind us now", xsplash gets more of bratsche's bandwidth
[17:10] <davidbarth> for the rest, the details are in the report: quickly
[17:10] <davidbarth> dx-lucid-application-indicator
[17:10] <davidbarth> Implementation completed; maintenance mode now
[17:10] <davidbarth> #524150 has been fixed and uploaded as a distro patch this afternoon
[17:11] <davidbarth> so a3 is safe with the session menu, even if you're not running gdm
[17:11] <davidbarth> dx-lucid-sound-indicator
[17:11] <davidbarth> several bug fixes (incl. mousewheel support in the right direction)
[17:11] <davidbarth> support for output device switching
[17:11] <davidbarth> dx-lucid-me-menu
[17:11] <davidbarth> bug fixes and support for the "me" entry
[17:12] <davidbarth> sorry, not #524150, that one is blocking app. indicator porters; currently being worked on
[17:12] <davidbarth> dx-lucid-session-menu
[17:12] <davidbarth> Implementation complete; maintenance mode
[17:12] <davidbarth> 506683: indicator-applet doesn't show menu choices when selected
[17:12] <davidbarth> that last one ^^ is now fixed and released
[17:12] <slangasek> hurray :)
[17:12] <davidbarth> yeah ;)
[17:13] <slangasek> (been fixed for me here for a while now, glad to see it's now fixed for everyone)
[17:13] <davidbarth> that's it for the report
[17:13] <davidbarth> dx questions?
[17:13] <davidbarth> well, there were probably two issues in this bug
[17:13]  * slangasek nods
[17:13] <davidbarth> but the first one was masking another error
[17:13] <slangasek> no questions here
[17:13] <slangasek> anyone else?
[17:13] <davidbarth> glad we kept it under the radar
[17:14] <slangasek> [TOPIC] Foundations Team
[17:14] <MootBot> New Topic:  Foundations Team
[17:14] <marjo> davidbarth: thx for the fix to 506683
[17:14] <slangasek> davidbarth: thanks
[17:14] <slangasek> is there anyone here representing Foundations this week?  (cjwatson is off today)
[17:15] <slangasek> [ACTION] slangasek to check with cjwatson Monday on status of Foundations a3 spec work
[17:15] <MootBot> ACTION received:  slangasek to check with cjwatson Monday on status of Foundations a3 spec work
[17:17] <slangasek> ScottK: foundations-lucid-supportable-binaries> if you've given me a link to the build test results, I think I've misplaced it; I could help unblock that if I had access to the data
[17:17] <slangasek> ScottK: (I think cjwatson has it, but we didn't get a chance to look at this during the sprint)
[17:17] <slangasek> no sense in dwelling on the rest of these specs, I think, unless others have questions?
[17:18] <persia> lucas sent it to the mailing list a couple weeks back: I'll hand you a URL if ScottK doesn't soon enough
[17:19] <slangasek> oh, that mailing list post has the details?  ok, great
[17:19] <slangasek> I can pull it from there
[17:19] <slangasek> [TOPIC] Security Team
[17:19] <MootBot> New Topic:  Security Team
[17:19] <slangasek> jdstrand: hi
[17:19] <persia> Not details, but a link to the rebuild failures :)
[17:20] <jdstrand> hi
[17:20] <jdstrand> as always: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <jdstrand> we are in good shape for alpha-3
[17:21] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <jdstrand> we finished all the stuff assigned to us
[17:21] <slangasek> well done :)
[17:21] <jdstrand> as for our essential bps, they are coming along-- the one assigned to kees in the above link actually has only one outstanding item that is assigned to me, and not tied to FF
[17:22] <jdstrand> thanks :) though we don't have nearly as much as other people due to our other obligations
[17:22] <jdstrand> the slow progress bp of mine (security-lucid-libvirt-apparmor-devel
[17:22] <jdstrand> ) does not have new features, and are just bug fixes
[17:22] <jdstrand> overall, we are in good shape for release
[17:23] <jdstrand> that's pretty much it from me
[17:23] <slangasek> ok
[17:23] <slangasek> any questions for security?
[17:24] <slangasek> [TOPIC] MOTU
[17:24] <MootBot> New Topic:  MOTU
[17:24] <slangasek> jdstrand: thanks
[17:24] <jdstrand> sure! :)
[17:25] <slangasek> no ScottK or sistpoty today
[17:25] <slangasek> persia: do you have anything you think is worth mentioning wrt MOTU?
[17:26] <persia> How is the motu-release/ubuntu-release merge progressing?  Is that complete?
[17:26] <persia> slangasek: I've not been following release issues closely.  I know there's heaps of NBS and FTBFS.  There's an issue with libSDL that the squeeze version doesn't work with some stuff we have, and the lucid version doesn't work with others.
[17:26] <slangasek> still some details being sorted out on list; the freeze exception process wiki will need updated.  Once that's all done, I'll send out another mail to u-d-a
[17:26] <persia> Dunno of anything else offhand.
[17:27] <slangasek> (I haven't done the actual team merge in LP yet, I think I can get that done today)
[17:27] <persia> Excellent.  I have seen requests for freeze exceptions in -motu.
[17:27] <slangasek> persia: ok - so business as usual then
[17:28] <slangasek> [TOPIC] AOB
[17:28] <MootBot> New Topic:  AOB
[17:28] <slangasek> anything more before we adjourn?
[17:28] <slangasek> anything that has people concerned regarding alpha-3 overall status?
[17:29] <slangasek> #endmeeting
[17:29] <MootBot> Meeting finished at 11:29.
[17:29] <slangasek> guess not :)
[17:29] <slangasek> thanks, all
[17:29] <apw> slangasek, thanks
[17:29] <marjo> slangasek: thx!