[15:55]  * slangasek waves
[15:55] <ttx> o/
[15:59] <pitti> o/
[15:59]  * JFo waves at slangasek 
[15:59]  * marjo waves
[16:00]  * JFo will do his best not to dump useless info in the middle of the meeting today :-)
[16:01]  * asac waves
[16:02] <slangasek> robbiew, Riddell, apw, njpatel, jdstrand: ping
[16:02] <njpatel> hey
[16:02]  * apw zones in
[16:02] <jdstrand> o/
[16:02] <robbiew> he
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> slangasek, There is already a meeting in progress.
[16:02] <robbiew> hey
[16:02] <Riddell> hi
[16:03] <slangasek> MootBot: lies
[16:03] <robbiew> lol
[16:03] <robbiew> #endmeeting
[16:03] <apw> #endmeeting
[16:03] <ttx> now that was short
[16:03] <robbiew> #endthef'ingmeeting! lol
[16:03] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-29
[16:03] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-29
[16:04] <slangasek> [TOPIC] Actions from previous meetings
[16:04] <slangasek>   * davidbarth to review cross-team assignments for dx specs and contact right people (DONE)
[16:04] <slangasek>   * apw to fix up state of bug #458537 to reflect reality
[16:04] <slangasek>   * asac and ScottK to review the plan for xulrunner demotion and present the resolution at the next meeting
[16:04] <apw> slangasek, that one is closed, so done
[16:04] <slangasek> excellent
[16:04] <asac> slangasek: so I didnt review the xulrunner demotion with scottk yet.
[16:04] <slangasek> asac: ok - this coming week, then?
[16:05] <asac> wanted to first have the short list of suggested rdepends ready.
[16:05] <asac> i hope so ... but there is sprint ;)
[16:05] <asac> but should be doable
[16:05]  * slangasek nods
[16:06] <slangasek> ok, now we've got a few changes in the presentation order today, because of some schedule conflicts... see the wiki page if you're easily startled by change :-)
[16:06] <slangasek> [TOPIC] Server Team
[16:06] <ttx> Thanks !
[16:07] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <ttx> Alpha3-targeted bugs:
[16:07] <ttx> A few MIR that are well in progress now
[16:07] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <ttx> Except one that still needs review (seabios)
[16:07] <ttx> bug 508870
[16:08] <ttx> Progress is expected on the eucalyptus bugs, since we'll be with Dan Nurmi of Eucalyptus next week
[16:08] <slangasek> (is it an ill-tempered seabios?)
[16:08] <ttx> Specs:
[16:09] <ttx> Only 2 < 25% in the Essential/High area:
[16:09] <ttx> server-lucid-uec-testing (9%)
[16:09] <ttx> This one was blocked on basic infrastructure access, but now mathias has access to a working UEC there (since yesterday)
[16:09] <ttx> So this is unblocked and should go smooth now.
[16:09] <ttx> One installer bug still prevents automatic install
[16:10] <ttx> We'll mention it later in the buglist-from-other-teams section
[16:10] <ttx> server-lucid-ec2-config (0%)
[16:10] <ttx> This is closely linked to the boothooks spec. Considering the two, global completion rate is 50%
[16:10] <ttx> Bugs affecting server, in other teams:
[16:10] <ttx> bug 512592
[16:11] <ttx> This one is impacting us, no assignee last time I looked
[16:11] <ttx> I targeted it to alpha3
[16:11] <ttx> bug 510130
[16:11] <ttx> This one is the next-in-list for the ramdiskless support on cloud images
[16:11] <slangasek> cjwatson: who should take 512592, you or ev?
[16:12] <ttx> also targeted to alpha3, and on jjohansen's plate.
[16:12] <cjwatson> ev, I'll cover it in my slot anyway
[16:12] <ttx> In other news, I think you got bug 506297 under control
[16:12] <ttx> That's all from me... Questions ?
[16:12] <slangasek> yes, 506297 just blocked on sorting an unrelated plymouth issue w/ Keybuk before uploading
[16:12] <slangasek> no questions here; anyone else?
[16:12] <ttx> Ah, another thing
[16:13] <ttx> server-lucid-eucalyptus-merging-and-packaging is at 44%, but new work items are expected today
[16:13] <ttx> maybe not enough to make it fall <25%, but...
[16:13] <ttx> kirkland is sdoing a pass on the bug list to nominate alpha3 targets
[16:14] <ttx> so we should have a better view on the work left in that spec next week.
[16:14] <ttx> That's really all for me now :)
[16:14] <slangasek> ok, thanks :)
[16:14] <slangasek> [TOPIC] Foundations Team
[16:14] <cjwatson> Targeted bugs:
[16:14] <cjwatson> bug 512592 - believed to be fixed as of last night's debian-installer upload (and ev has closed this now); please report recurrences
[16:15] <cjwatson> bug 477104 - fixed upstream, will deal with testing for karmic at sprint
[16:15] <cjwatson> various plymouth-related issues to be resolved at sprint (bug 506709, bug 500198, bug 506418)
[16:15] <cjwatson> Feature work:
[16:15] <cjwatson> foundations-lucid-gfxboot-update: still blocked on DX, on sprint agenda (cjwatson/bratsche)
[16:15] <cjwatson> foundations-lucid-software-center-repository-based-index/foundations-lucid-index-based-downloads-client: server/client pair between Soyuz and mvo; substantial work involved, may be difficult to land, at risk
[16:15] <cjwatson> foundations-lucid-boot-experience: just kdm to go; should this be tracked by desktop at this point?
[16:15] <cjwatson> foundations-lucid-reliable-device-id-in-grub: further along than it looks from the completion rate; code is in a branch/PPA and should be finished off at the sprint
[16:15] <cjwatson> foundations-lucid-supportable-binaries: ScottK said last week that our volunteer disappeared, so I've put this on our sprint agenda
[16:15] <cjwatson> foundations-lucid-fix-iscsi-root: having a hard time getting a response from one of the bug reporters here, but once cjwatson completes the discussion with QA it should be relatively easy to flush this out
[16:15]  * ttx suspects cjwatson of cheating, nobody types that fast.
[16:16] <pitti> cjwatson: remaining foundations-lucid-boot-experience WI is on our radar
[16:16] <cjwatson> ttx: cheating in this way is positively encouraged in the release meeting :-)
[16:16] <cjwatson> pitti: good, thanks
[16:16] <pitti> ttx: I wish there was teh reading counterpart of copy&paste :)
[16:17] <cjwatson> (done, anyway)
[16:17]  * robbiew assumes (and hopes) the daily boot charting will resume once Keybuk returns next week?
[16:18] <cjwatson> it might be the week after since Keybuk won't be at home - not sure
[16:18] <slangasek> robbiew: given that Keybuk's return next week is to Portland, not England, I'm not sure it will
[16:18] <pitti> in the meantime, http://people.canonical.com/~pitti/bootcharts/ has my daily measuring and experiments
[16:18] <slangasek> Reboots were Needful
[16:18] <robbiew> bah!
[16:18] <robbiew> okay
[16:18] <cjwatson> oh, and I'm going to shift 506418's milestone up to alpha-3, to go with the other similar plymouth-related bugs
[16:18] <pitti> it's not Scott's nicely automated one, though
[16:18] <pitti> setting that up is on desktop team's sprint agenda (sit down with Scott)
[16:19]  * ogra doesnt reboot daily but has an awesomly fast boot to report
[16:19] <pitti> ogra: 10 s!
[16:19] <ogra> yeah !
[16:19] <ogra> 3 to X
[16:19] <ogra> i'll show off with it at the sprint :)
[16:19]  * apw wants to see that
[16:20] <slangasek> any questions for foundations?
[16:20] <slangasek> cjwatson: do mvo's at-risk specs require any follow-up at this point?
[16:21] <slangasek> [TOPIC] Kernel Team
[16:21]  * slangasek takes that out-of-band
[16:21] <slangasek> cjwatson: thanks
[16:21] <slangasek> apw: hi
[16:22] <apw> yo
[16:22] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  The bulk of the items pushed out from Alpha-2 are now done, with one minor item for Apparmor having completed in part (and split into two items).  We remain above the line on our burn-down chart dispite a number of items completing, in part this is due to the linking of bugs to blueprints bringing outstanding work to light.  We will be
[16:22] <apw> reviewing this at the platform sprint to determine if we need to push out any items.  Remaining items for Alpha-3 are at the second URL below:
[16:22] <cjwatson> slangasek: I think there's probably no value in following up right now vs. Monday
[16:22] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:22] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:22] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:22] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:22] <apw> We now have a linux-backports-module package containing a Nouveau backport available in PPA for testing, preliminary testing is encouraging; evaluation planned for next week.    Suspend-resume testing images are close to completion (planned for use at SCALE), images should be available next week for early testers.  Work on the ubuntu-delta has been slow this week, but we still expect to hit alpha-3.  The two bugs called out both require re-testin
[16:22] <apw> g (which is pending) as we have shipped major updates to those kernels.
[16:22] <apw> The distro kernel is now pulled up to v2.6.32.6 and is looking pretty stable in testing, the disabling of i915.powersave has improved user experience dramatically; we are expecting fixes in this area via -stable shortly.  The fsl-imx51 arm branch gained a large update to the BSP from Freescale which is now in the archive.  The mvl-dove updated v2.6.32 based BSP branch is now also in the archive.
[16:22] <slangasek> cjwatson: indeed
 ... and thanks for bumping me up
[16:23]  * ttx disappears for last minute packing and traincatching
[16:24] <slangasek> any questions for kernel?
[16:25] <pitti> apw: is nouveau still realistic for alpha-3?
[16:25] <pitti> apw: this is a "alpha-3 or lucid+1" kind of change, I think
[16:25] <apw> we have a working nouveau backport it seems, some testing etc to do next week to confirm that on more h/w
[16:26] <pitti> sweet
[16:26] <slangasek> great
[16:26] <apw> the plan is to evaluate and discuss next week, your input would be appreciated
[16:26] <slangasek> the "or lucid+1" option isn't very appealing
[16:26] <pitti> slangasek: well, I'm not that hot on enabling this late, like in beta-2
[16:26] <marjo> pitti: +1
[16:26] <apw> and any nvidia h/w you have with you could you let me and bryce know
[16:27] <pitti> it would be awesome to get, but we should get it early for maximum testing
[16:27] <marjo> slangasek: why "lucid +1" not appealing?
[16:27] <slangasek> pitti: I agree with you that enabling it post-alpha3 is too late
[16:27] <pitti> apw: too bad that most of us have intel graphics in their laptops nowadays..
[16:27] <pitti> (for the sprint)
[16:27] <pitti> but we can try some hotel computers with an USB stick
[16:27] <pitti> (half serious)
[16:27] <apw> slangasek, i want the decision next week based on whether we can test and deliver for A-3
[16:27] <slangasek> marjo: because kms support is dependent on nouveau, and the non-kms boot experience is well sub-par
[16:28] <pitti> apw: sounds great
[16:28] <slangasek> apw: understood
[16:28] <marjo> slangasek: ok, will follow up w/ pgraner & rickspencer3
[16:28] <slangasek> [TOPIC] QA Team
[16:28] <slangasek> apw: thanks
[16:28] <marjo> HW Testing
[16:28] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:28] <marjo> Netbooks:
[16:28] <marjo> Passed:   9 (69%)        Failed:   3 (23%) Untested: 1 ( 8%)
[16:28] <marjo> Laptops:
[16:28] <marjo> Passed:  22 (85%)        Failed:   1 ( 4%) Untested: 3 (11%)
[16:28] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:28] <marjo> Servers:
[16:28] <marjo> Passed:  52 (98%)        Failed:   0 ( 0%) Untested: 1 ( 1%)
[16:28] <marjo> Desktops:
[16:28] <marjo> Passed:  12 (100%)		Failed:   0 (  0%) Untested: 0 (  0%)
[16:28] <marjo> Bugs:
[16:28] <marjo> -----
[16:28] <marjo> Open bugs:
[16:28] <marjo> LP: #510795  No sound when headphones plugged in on HP Mini 500 (Undecided,
[16:29] <marjo> New)
[16:29] <marjo> LP: #504315  Toshiba NB100 failed to resume from hibernate (Undecided,
[16:29] <marjo> Confirmed)
[16:29] <marjo> LP: #497546  Microphones not working on Dell Vostro 320 (Undecided, New)
[16:30] <slangasek> I see the same hw testing failures as before... do these bugs need escalated?
[16:30] <mdeslaur> hey guys, I've got nvidia hardware and will be at the sprint next week
[16:30] <mdeslaur> apw, pitti: ^
[16:31] <apw> mdeslaur, excellent
[16:31] <fader_> slangasek: I believe so -- I haven't seen any updates on them since last week
[16:31] <slangasek> [ACTION] slangasek to poke priorities of hw testing bugs
[16:31] <apw> are those three all kernel bugs?  if so poke JFo to get them on our list
[16:32] <slangasek> marjo: anything that needs discussed about the specs?
[16:32] <fader_> apw: My suspicion is yes, as they're audio/hibernate bugs
[16:32] <slangasek> apw: the first is assigned to the desktop, oddly
[16:32] <marjo> slangasek: no
[16:32]  * slangasek reassigns 510795 to the kernel
[16:33] <pitti> that seems odd
[16:33] <pitti> it's certainly not a gst-python problem
[16:33] <apw> odd assignement of bugs is normal in launchpad
[16:33]  * JFo puts 510795 on the list
[16:33] <slangasek> any other questions for QA?
[16:33] <robbiew> marjo: do you still plan to replicate Keybuks daily bootchart reporting with the hardware in the lab?  I think cr3 already has the data, just need to steal his scripts for parsing and reporting, right? Maybe something worth tackling at the sprint next week.
[16:33] <pitti> looks like a checkbox bug
[16:34] <marjo> robbiew: yes, part of cr3's task list
[16:34] <robbiew> nice...thanks
[16:35] <marjo> slangasek: want update on alpha2 bugs?
[16:35] <apw> marjo, amitk likely would be intrested in the how part of that at sprint too
[16:35] <slangasek> marjo: if you have it
[16:35] <marjo> * alpha-2 test report update
[16:35] <marjo> [16:35] <marjo> LP: #505772 - system freezes sometimes after X is up for a while - Fix Released - Critical
[16:35] <marjo> LP: #506683 - indicator-applet doesn't show menu choices when selected - Confirmed - Critical
[16:35] <marjo> [16:35] <marjo> LP: #506297 - Graphical Ubuntu logo enabled on servers, no more login prompt - Fix Committed - High
[16:35] <marjo> LP: #500198 - casper-md5check needs to be ported to plymouth - Triaged - High
[16:35] <marjo> LP: #503180 - eucalyptus-cloud doesn't reply to requests - Confirmed - High
[16:35] <marjo> LP: #506717 - [Lucid] plymouth does not display when using nvidia drivers  - Fix Committed - High
[16:35] <marjo> LP: #506805 - quassel built without ssl support - Fix Released - High
[16:35] <marjo> LP: #506816 - wl missing after Karmic -> Lucid upgrade - New - High
[16:35] <marjo> LP: #507343 - Ubiquity crashed in OEM configuration - New - High
[16:36] <marjo> two are "new" will follow up w/ engineers
 LP: #506816 - wl missing after Karmic -> Lucid upgrade - New - High
[16:36] <marjo> that's all folks
[16:36] <apw> isn't that normal behaviour?
[16:36] <apw> i thought jockey disabled all binary drivers on update
[16:36] <marjo> apw: huh?
[16:37] <pitti> that moved from linux-restricted-modules to dkms?
[16:37] <pitti> apw: s/disable/does not automatically enable/
[16:37] <apw> it was dkms in karmic too
[16:37] <apw> ahh hrm, then its broken, ignore me
[16:37] <pitti> oh, misread, sorry
[16:37] <pitti> that should be taken care of by dkms actually
[16:38] <slangasek> does that bug need reassigned, then?
[16:40] <slangasek> pitti: can you review if it needs reassigned to dkms?
[16:40] <pitti> yes, can do
[16:40] <marjo> pitti: thx
[16:40] <slangasek> [ACTION] pitti to triage bug #506816 to see if it's a dkms bug
[16:40] <slangasek> any other questions?
[16:40] <pitti> (actually it looks just fine, but will followup there)
[16:41] <marjo> slangasek: thx
[16:41] <slangasek> [TOPIC] Desktop Team
[16:41] <slangasek> marjo: thank you!
[16:41] <slangasek> pitti: your turn
[16:41] <pitti> as usual, weekly report/bug status/spec status is at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:41] <pitti> this week's progress:
[16:41] <pitti> - Lots of work on desktop-lucid-startup-speed; current state of the art is 7.5 s
[16:41] <pitti> - Updated GNOME to 2.29.6
[16:42] <pitti> - Landed simple-scan (removed xsane)
[16:42] <pitti> - Moved to OO.o 3.2, sorted out the MIRs around it, etc.
[16:42] <pitti> - Some progress on desktop-lucid-social-from-the-start
[16:42] <pitti> RC Bug front remains relatively calm; we did not get to much bug fixing, due to focussing on boot speed
[16:42] <pitti> oh, the 7.5 s is the desktopish part only, of course
[16:43] <Riddell> Kubuntu..
[16:43] <pitti> the new UNE might be in jeopardy; depends on sabdfl decision and upstream progress, we'll settle that next week
[16:43] <Riddell>  * new {k,gnome,}packagekit 0.5 uploaded
[16:43] <Riddell>  * KDE SC 4.4 tagging due next week
[16:43] <Riddell>  * MIRs outstanding for KOffice: plotutils, opengtl, libspnav, getfem++, pstoedit, libqtgtl
[16:43] <Riddell>  * python-qt/kde in (unblocks jockey and others) but having problems compiling on ARM
[16:43] <Riddell>  * https://wiki.ubuntu.com/Kubuntu/Todo
[16:43] <slangasek> not much movement on the two low-completion specs from last week; sprint, I guess?
[16:43] <pitti> slangasek: right, that or defer parts
[16:44] <pitti> slangasek: the important bits are on the sprint agenda
[16:44] <slangasek> pitti: what does that mean, "the new UNE"?
[16:44] <slangasek> I'm not thinking you mean it's questionable whether we'll ship UNE w/ 10.04
[16:44] <pitti> slangasek: no, in the worst case we'll just ship with the current netbook-launcher
[16:45] <slangasek> ok
[16:45] <pitti> for now, all I can say that it might not land in a3
[16:45]  * slangasek nods
[16:45] <pitti> (as mentioned in "intrusive chagnes for A3")
[16:46] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:46] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:47] <slangasek> any questions for desktop?
[16:48] <slangasek> [TOPIC] DX Team
[16:48] <njpatel> Hi -- I'm standing in for dbarth, as he's in training today
[16:48] <slangasek> pitti, Riddell: thanks
[16:48] <slangasek> njpatel: thought you might be :)
[16:48] <njpatel> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:48] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:48] <njpatel> Burn down chart: http://people.canonical.com/~pitti/workitems/canonical-dx-team-lucid-alpha-3.html
[16:48] <njpatel> Desktop
[16:48] <njpatel> No releases this week
[16:48] <njpatel> Blueprints tracked for alpha-3:
[16:48] <njpatel> dx-lucid-application-indicator
[16:48] <njpatel> dbusmenu performance analysis completed; performance on track with requirements
[16:48] <njpatel> slight improvements to the protocol (cross-compatibility & performance)
[16:48] <njpatel> dx-lucid-gtk-improvements
[16:48] <njpatel> support for indicator object display for dbusmenu: slider & text entry
[16:48] <njpatel> cs-deco support progressing well
[16:48] <njpatel> dx-lucid-sound-indicator
[16:48] <njpatel> UI mostly implemented; integration with PA progressing (volume control signal)
[16:48] <njpatel> Netbook (UNR)
[16:48] <njpatel> Blueprints tracked for alpha-2:
[16:48] <njpatel> dx-lucid-netbook-launcher-startup-speed
[16:48] <njpatel> wncksync performance improvements landed on trunk
[16:49] <njpatel> and echo what pitti said about UNE
[16:49] <njpatel> slangasek, go easy on me -- I know nothing ;-)
[16:49] <slangasek> heh :)
[16:49] <pitti> njpatel: will you be at the sprint? would like to sit down with you wrt. launcher-startup-speed
[16:50] <njpatel> pitti, yep will be
[16:50] <njpatel> pitti, sounds good
[16:51] <slangasek> no questions here - anyone else?
[16:51] <slangasek> [TOPIC] Mobile Team
[16:51] <slangasek> njpatel: thanks
[16:52] <asac> hi
[16:52] <asac> summary for mobile:
[16:52] <asac> * uboot postponed
[16:52] <asac>  -> too many bugs, so we stoped investing efforts and use redboot for imx51
[16:52] <slangasek> "postponed" - post-lucid?
[16:53] <asac> opportunity ... but not for long anymore ... we basically handed a couple of essential bugs upstream
[16:53] <asac> if they fix that in time we will reconsider ... the debian-cd work etc. is already done
[16:53] <asac> but realistically i dont think that it will happen anymore
[16:53] <ogra> slangasek, probably not even post lucid
[16:53] <slangasek> how are you defining "in time"?
[16:54] <ogra> it stands and falls with a driver for USB which nobody is working on upstrem
[16:54] <asac> slangasek: they have  code drop mid february
[16:54] <asac> if thats not in there, then there is no way imo
[16:54] <robbiew> so perhaps "* uboot dropped" as it pertains to Lucid
[16:54] <ogra> yes
[16:54] <asac> yes
[16:55] <ogra> unless you like to see us hacking debian-cd to produce three partition based liveimages and other awful hacks :)
[16:55] <asac> * marvel dove + thumb2 hangs -> no progress ... we will have the latest hardware at sprint - and will take a decision on this
[16:55] <asac> based on what we find there
[16:55] <asac> * lightweight browser: chromium-browser and firefox 3.6 in the archive!
[16:55] <ogra> \o/
[16:55] <asac> we already have a first round of benchmarks
[16:56] <robbiew> nice
[16:56] <asac> which yield interesting results ... so we are verifying
[16:56] <asac> for now ffox36 on arm seems to be faster for spidermonkey
[16:56] <slangasek> "interesting results" - firefox also takes < 10s to boot? :-)
[16:56] <asac> hehe
[16:56] <robbiew> heh
[16:56] <ogra> *g*
[16:57] <asac> the other dromaeo bench is in favor of chromium
[16:57] <cjwatson> ogra: well, if we can ever manage to get some hardware to ship out, there's a standing offer from a grub2 developer ...
[16:57] <ogra> yeah
[16:57] <asac> both are javascript benchmarks
[16:57] <ogra> cjwatson, its high on my list at my office wall ...
[16:57] <ogra> :)
[16:57] <asac> we will also do startup benchmarking ... unfortnuately we wont have real rendering benchmarks ...
[16:57] <asac> but will use user perception
[16:57] <asac> for that part
[16:57] <asac> * first lsb lib-test run; raw results available on wiki page
[16:58] <asac> so thats good news, but we have a few bugs so we will fix those and redo the tests
[16:58] <asac> during sprint
[16:58] <asac> * thumb2 review finished and outstanding porting bugs filed.
[16:58] <asac> https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList#High/Medium Prority Packages
[16:58] <ogra> mono sadly makes our images break atm
[16:58] <asac> [LINK] https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList#High/Medium Prority Packages
[16:58] <MootBot> LINK received:  https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList#High/Medium Prority Packages
[16:58]  * ogra thinks that should be noted
[16:58] <asac> so ...
[16:58] <asac> image status:
[16:59] <ogra> whoops, sorry i was to fast
[16:59] <asac> * general: image production broken by mono (514215) and crashes by gvfs (512959)
[16:59] <asac> i am fixing mono right now ... and gvfs has a tight regression window, so should be fixable too
[16:59] <asac> * imx51: in good shape.
[16:59] <ogra> yeah, we'll get that done next week
[16:59] <asac> * dove: not in good shape (thumb2 board hangs - 504880 and 505772)
[16:59] <asac> as already explained above :/
[17:00] <asac> on work item front things look ok ...
[17:00] <asac> [LINK]  http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[17:00] <MootBot> LINK received:   http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[17:00] <asac> [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html
[17:00] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html
[17:01] <asac> and RC Bugs does not show anything scary on top of what i already mentioned wrt dove
[17:01] <slangasek> asac: what's going on with liquid?  I don't see any cronjob changes yet; are we going to have this in place for A3?
[17:01] <asac> slangasek: thats a community effort that we embrace and help with.
[17:01] <asac> i think for A3 all the packages ar realistic ... whether we will build an image or not is not sure
[17:02] <ogra> i think there were about two or three packages missing that are in review atm
[17:02] <asac> REVU
[17:02] <slangasek> ah
[17:02] <asac> yes.
[17:02] <asac> questions?
[17:02] <slangasek> no other questions here
[17:02] <slangasek> anyone else?
[17:03] <ScottK> asac: Could we get some help with python-qt4 on armel?
[17:03] <asac> ScottK: is that on the https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList#High/Medium Prority Packages list?
[17:03] <ogra> i thought NCommander is already on it
[17:03] <ScottK> He may be.
[17:03] <asac> i would hope it is there if there are issues atm
[17:03] <asac> ScottK: there is qt4-x11
[17:03] <asac> is that the source?
[17:04] <ScottK> No, it's python-qt4
[17:04] <ogra> its likely not thumb related
[17:04] <asac> hmm. ok. if there is a bug and ncommander is assigned it should be ok
[17:04] <ogra> we have issues with it every release
[17:04] <ScottK> OK.
[17:04] <ScottK> New dh_sip coming that should help
[17:05] <asac> ok
[17:05] <ScottK> (in general, not this one build failure)
[17:05] <asac> ScottK: ensure that there is a bug and is targetted/milestoned please
[17:05] <ScottK> Will do.
[17:05] <asac> ok anything else?
[17:05] <ScottK> Not from me
[17:05] <asac> thx
[17:06] <slangasek> [TOPIC] Security Team
[17:06] <slangasek> asac, ogra: thanks
[17:06] <slangasek> jdstrand: hi
[17:06] <ogra> thanks
[17:06] <asac> thx
[17:06] <jdstrand> o/
[17:06] <jdstrand> as always: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:07] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:07] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:07] <jdstrand> no big issues this week
[17:07] <jdstrand> I do want to point out that security-lucid-libvirt-apparmor-devel is now Slow Progress
[17:08] <jdstrand> to better reflect reality
[17:08] <slangasek> what was it previously?
[17:08] <jdstrand> Good Progress
[17:08]  * slangasek nods
[17:08] <jdstrand> it is a time thing, not any technical issues
[17:08] <jdstrand> also, our burndown still looks good, but we are touching the line the week
[17:09] <jdstrand> there are some things that will be marked DONE likely by the end of the day today, so we should be under it
[17:09] <jdstrand> (otherwise early next week)
[17:10] <slangasek> great :)
[17:10] <jdstrand> that's pretty much it unless people have questions
[17:10] <slangasek> no questions here; others?
[17:11] <slangasek> [TOPIC] MOTU
[17:11] <slangasek> jdstrand: thanks
[17:11] <slangasek> ScottK: hello
[17:11] <jdstrand> sure! :)
[17:11] <ScottK> Hello
[17:11] <ScottK> I got confirmation that the person who was working on the supportable binaries analysis can't do it due to health issues.
[17:11]  * slangasek nods
[17:11] <ScottK> Need a volunteer, but didn't have time to deal with asking for one.
[17:12] <slangasek> cjwatson said he was putting the spec on the sprint agenda
[17:12] <ScottK> Same thing with the action with asac on xulrunner.
[17:12] <ScottK> Ah, excellent.
[17:12] <slangasek> you have the data set for that, right?  Can you get it to cjwatson or myself over the weekend?
[17:12] <ScottK> I've got a start of a python script that he had done if anyone wants it.  I haven't even opened it to look at it.
[17:13] <ScottK> I do have the data.
[17:13] <ScottK> I'll send it to you both.
[17:14] <ScottK> Do to declining time available for Ubuntu stuff I'm probably going to ask someone else to start reporting on MOTU in the release meetings.
[17:14] <ScottK> Do/Due
[17:14] <ScottK> That's all I have.
[17:14] <slangasek> alright
[17:14] <slangasek> thanks for your efforts keeping us up-to-date until now!
[17:15] <slangasek> anyone have questions regarding MOTU?
[17:15] <slangasek> [TOPIC] AOB
[17:15] <slangasek> anything else before we wrap?
[17:16] <slangasek> #endmeeting
[17:16] <slangasek> done
[17:16] <pitti> thanks everyone
[17:16] <slangasek> thanks, all - safe travels if you're traveling this weekend!
[17:16] <ogra> yay
[17:16] <ogra> slangasek, ejoy the quietness in the channels while we all trave :)
[17:16] <ogra> +l