[03:34] <TVrotsurbrain> s
[03:35] <TVrotsurbrain> !ops
[03:36] <HFSPLUS> !ops
[03:36] <Vantrax> nice
[15:58]  * slangasek waves
[15:58] <pitti> o/
[15:58] <ttx> o/
[15:59] <robbiew_> \_O_/
[15:59] <jiboumans>  /o\
[15:59] <slangasek> o<
[15:59]  * asac waves
[16:00] <Riddell> hi release dudes
[16:01]  * ogra moos
[16:01]  * apw arrives
[16:02] <slangasek> marjo / fader_ / sbeattie, ScottK, davidbarth, jdstrand: ping
[16:02] <slangasek> #startmeeting
[16:02] <ScottK> o/
[16:02]  * fader_ waves.
[16:02]  * marjo waves
[16:02] <jdstrand> o/
[16:02] <slangasek> hi, folks
[16:02]  * davidbarth waves as well
[16:02] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-22 - agenda
[16:02] <slangasek> hmm, botless again?
[16:03] <slangasek> [TOPIC] actions from previous meetings
[16:03] <slangasek>   * davidbarth to review cross-team assignments for dx specs and contact right people
[16:03] <slangasek>   * ev to retarget foundations-lucid-gfxboot-update greeter to alpha-3
[16:03] <slangasek>   * seb128 to follow up with pitti wrt lucid-ubuntu-one-symlinks-and-udfs not tracked on the desktop team report
[16:03] <slangasek> davidbarth: any progress?
[16:03] <slangasek> pitti: I think seb128's is done since you talked to me about this, so this is resolved now, yes?
[16:04] <pitti> I think so
[16:04] <pitti> it was an outdated teams table
[16:04] <slangasek> and the spec retarget is done
[16:04] <pitti> fixed permanently now
[16:05] <slangasek> thanks
[16:05] <slangasek> [TOPIC] Outstanding work items still targeted to alpha-2
[16:05] <davidbarth> slangasek: sure, i've checked all bp and contacted (you, the mail is still here opened) for the right foundation contact; all other bp covered and no holes
[16:05] <slangasek> davidbarth: great, thanks :)
[16:05] <pitti> 0 for desktop
[16:06] <slangasek> alpha-2 stuff - there were only 4 of these left, so wanted to bring attention to them as a whole rather than by team
[16:06] <asac> i thought i postponed everything
[16:06] <slangasek>   * Bug:504723: [MIR] uboot-imx
[16:06] <slangasek>   * UbuntuSpec:dx-lucid-gtk-improvements: [bratsche] Identify and fix broken apps - totem
[16:06] <slangasek>   * UbuntuSpec:security-lucid-bios-notifier: integrate tool into landscape motd
[16:06] <slangasek>   * Bug:506761: lucid uboot hangs on fatload uImage on fsl TO2 TO2.5 and TO3
[16:06] <jdstrand> I just updated security-lucid-bios-notifier
[16:06] <slangasek> asac: you have some linked bugs that weren't targeted
[16:06] <ogra> uboot-imx was approved today, i didnt add it to supported yet
[16:07] <asac> slangasek: yes, i missed the bug.
[16:07] <slangasek> davidbarth: and one last item there for you guys - I guess that should be retargeted to alpha-3 also?
[16:08] <davidbarth> slangasek: you should have the email now
[16:08] <asac> moved milestone of uboot spec to alpha-3 now (though all items where moved already)
[16:08] <davidbarth> right
[16:08] <asac> so both bugs should be postponed too now
[16:08] <slangasek> ok - that'll be the last mention of alpha-2 WIs from me :)
[16:08] <davidbarth> this one needs to reintegrated
[16:09] <slangasek> [TOPIC] QA Team
[16:09] <slangasek> marjo, fader_: hi
[16:09] <marjo> HW Testing
[16:09] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:09] <marjo> Netbooks:
[16:09] <marjo>         Passed: 9 (69%) Failed: 3 (23%) Untested: 1 (8%)
[16:09] <marjo> Laptops:
[16:09] <marjo>         Passed: 26 (100%) Failed: 0 (0%) Untested: 0 (0%)
[16:09] <marjo> Servers:
[16:09] <marjo>         Passed: 51 (96%) Failed: 0 (0%) Untested: 2 (4%)
[16:09] <marjo> Desktops:
[16:09] <marjo>         Passed: 12 (100%) Failed: 0 (0%) Untested: 0 (0%)
[16:09] <marjo> Bugs:
[16:09] <marjo> -----
[16:09] <marjo> New bugs:
[16:09] <marjo> 510795  No sound when headphones plugged in on HP Mini 500 (Undecided,
[16:09] <marjo> New)
[16:09] <marjo> 510710  ubiquity crashed with NameError in progress_loop() (Undecided,
[16:09] <marjo> Fix Released)
[16:09] <marjo> Open bugs:
[16:09] <marjo> 510795  No sound when headphones plugged in on HP Mini 500 (Undecided,
[16:09] <marjo> New)
[16:09] <marjo> 504315  Toshiba NB100 failed to resume from hibernate (Undecided,
[16:09] <marjo> Confirmed)
[16:10] <marjo> 497546  Microphones not working on Dell Vostro 320 (Undecided, New)
[16:10] <marjo> fader will follow up w/ all outstanding bugs
[16:10] <marjo> Specs status and burn-down chart:
[16:10] <marjo> http://people.canonical.com/~pitti/workitems/canonical-qa-lucid-alpha-3.html
[16:11] <marjo> * UbuntuSpec:lucid-qa-checkbox-integrate-regression-testing
[16:11] <marjo> [cr3] Integrate into hardware certification to run on a per milestone basis: DONE
[16:11] <marjo> * UbuntuSpec:qa-lucid-automated-server-testing
[16:11] <marjo> On track for Alpha-3
[16:11] <marjo> * UbuntuSpec:lucid-qa-kernel-test-automation
[16:11] <marjo> [leannogasawara] gcov kernel testing to evaluate kernel coverage (ogasawara to build kernel, talk to fader for testing): TODO
[16:11] <marjo> Shooting for completion today.
[16:11] <marjo> [cr3] Merge kernel team test scripts into checkbox: TODO
[16:11] <marjo> Changed to INPROGRESS
[16:11] <pitti> are the netbook failures mainly due to the sound problems, or something worse?
[16:12] <fader_> pitti: sound on the HP Mini but hibernate on everything else
[16:12] <fader_> Hibernate seems to be really broken at the moment
[16:12] <pitti> ah, but hiberation is broken in general, not just on netbooks
[16:12] <marjo> pitti: ack
[16:13] <marjo> * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:13] <marjo> [cr3] Extract CPU- and I/O-data provided by bootchart: TODO
[16:13] <marjo> [cr3] Add DX PPA when testing and reboot if new packages are discovered: INPROGRESS
[16:13] <marjo> Will start after lucid-qa-kernel-test-automation tasks are completed.
[16:13] <pitti> (the desktop/laptop ones said 100%)
[16:13] <fader_> pitti: Those have had only automated testing at the moment which did not hit hibernate; we're planning a round of manual tests as well
[16:13] <fader_> So expect to see more failures when we do if hibernate is still broken :/
[16:14] <slangasek> pitti: is there a bug # for "hibernate is generally broken"?
[16:14] <slangasek> or does 504315 cover that?
[16:14] <pitti> bug 499940
[16:15] <slangasek> ok
[16:15] <marjo> slangasek: that's all folks
[16:15]  * pitti dupes
[16:16] <slangasek> marjo, fader_: is there a follow-on to the alpha-2 ISO testing report, showing how well we're doing at fixing the bugs that were reported?
[16:17] <marjo> slangasek: i checked on the critical bugs and they are all assigned and/or confirmed
[16:17] <slangasek> but not fixed yet, ok :)
[16:17] <marjo> ack
[16:17] <slangasek> marjo, fader_: thanks
[16:17] <slangasek> [TOPIC] Desktop Team
[16:17] <slangasek> pitti, Riddell: you're on
[16:17] <pitti> Weekly summary: (details on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus)
[16:17] <pitti> - Boot speed goal is now officially for UNE; desktop-lucid-startup-speed updated accordingly
[16:17] <pitti> - Rearranged startup to have fewer interdependencies, speed up wncksync, gnome-settings-daemon, seahorse
[16:18] <pitti> - New GNOME point release
[16:18] <pitti> - X.org wacom driver should work again
[16:18] <pitti> - bug front: I went through the lucid bugs to review the desktop-ish ones, which added a few things to our list; under control by and large, though
[16:18] <pitti> related to boot speed, I noticed a 5 second regression when 2.6.32-11 landed, filed as bug 510937
[16:18] <pitti> not confirmed by someone else yet
[16:18] <pitti> just as an early warning
[16:18] <pitti> We have quite a high number of WIs for alpha-3, and I fully expect that we'll drop some.
[16:18] <pitti> The rationale is that some of the specs are "alpha-3 or not at all for lucid" (like nouveau), and some others are targets of opportunity (like social-from-the-start) which we don't want to pursue later any more (when we want to concentrate on bug fixing).
[16:19] <slangasek> pitti: "now officially for UNE" - meaning we are no longer planning to hit 20 secs with the desktop image?
[16:19] <pitti> slangasek: we have 20 already
[16:19] <pitti> 10 is the goal
[16:19] <slangasek> er, 10
[16:19] <pitti> but there's no way that we can do that with a standard GNOME install
[16:19] <pitti> with compiz, evo, themes, and all those bells and whistles
[16:20] <robbiew_> would require us to make non-LTS like changes ;)
[16:20] <pitti> many optimizations apply to both gnome and une of course, but the 10 second mark is une only
[16:20] <slangasek> alright
[16:20] <Riddell> Kubuntu?
[16:21] <pitti> I'm done, so go ahead please
[16:21] <Riddell> KDE SC 4.4 RC 2 due to be uploaded tonight
[16:21] <Riddell> MIRs outstanding
[16:21] <Riddell> virtuoso-opensource 503774 some packaging work to be done
[16:21] <Riddell> New SIP and KOffice 2 both still in progress
[16:21] <Riddell> Qt4 changing to ibus by default from XIM
[16:21] <Riddell> https://wiki.ubuntu.com/Kubuntu/Todo
[16:21] <Riddell> i386 ISO is no longer oversized
[16:21] <pitti> qt4 ibus> nice
[16:21] <Riddell> still working on pesky amd64
[16:21] <pitti> are there any langpacks to chop still?
[16:22] <Riddell> the qt 4 change will be a simple config patch from us but upstream are looking to do the same thing
[16:22] <Riddell> no we don't have any langpacks
[16:23] <slangasek> you've gotten rid of the extra libicu?
[16:23] <Riddell> yes that went a while ago
[16:24] <pitti> virtuoso is not even on the CD yet, right?
[16:24] <Riddell> no that'll be something else right enough
[16:24] <pitti> time to chop OO.o perhaps and just ship koffice? (and perhaps make it very easy to install)
[16:25] <Riddell> always tempting but nobody quite has the guts to do it
[16:25] <pitti> or would that make folks go wild?
[16:25] <Riddell> I've not looked closely at the problem anyway, I need to go over germinate output and see what shouldn't be there
[16:25] <Riddell> koffice isn't suitable currently, it's still going through its KDE 4 transition
[16:26] <ScottK> And has never been sufficiently interoperable.
[16:26] <mhall119|work> is Kubuntu going to be LTS this time around?
[16:26] <ScottK> Yes
[16:26] <slangasek> you'll keep us posted on the progress, then?
[16:26] <Riddell> mhall119|work: yes
[16:26] <mhall119|work> cool
[16:26] <Riddell> slangasek: yes indeed
[16:27] <slangasek> ok. any other business for desktop?
[16:27] <slangasek> [TOPIC] DX Team
[16:27] <slangasek> pitti, Riddell: thanks
[16:27] <slangasek> davidbarth: hi
[16:27] <davidbarth> slangasek: hi
[16:27] <davidbarth> The weekly report is up at the usual place: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:28] <davidbarth> This week we've played the planning game for the next 4 weeks, with an intermediate milestone set for the time we hit the platform sprint
[16:28] <davidbarth> of note for this week:
[16:28] <davidbarth> A3 plan updated, with a more limited focus
[16:29] <davidbarth> dx-lucid-application-indicator
[16:29] <davidbarth> dbusmenu performance analysis ongoing
[16:29] <davidbarth> new indicator-application 0.0.10-0ubuntu1 released this week: icon ordering, bug fixes, startup fixes
[16:29] <davidbarth> new indicator-me-0.2.1-0ubuntu1: integrated distro comments
[16:29] <davidbarth> indicator-applet-0.3.2-0ubuntu1: ordering, logging
[16:29] <davidbarth> libindicator-0.3.1-0ubuntu1: ordering update, service restarting support
[16:29] <davidbarth> so a lot of work on polishing the new indicators
[16:29] <davidbarth> we have an outstanding bug, discovered by seb
[16:30] <davidbarth> seb128 that is, ted is still chasing it as we speak
[16:30] <slangasek> davidbarth: report lists dx-lucid-netbook-launcher-startup-speed as "finished for A2", but there are outstanding WIs that were retargeted to A3; this is still on the team's radar, right?
[16:30] <davidbarth> #506683
[16:30] <davidbarth> slangasek: indeed
[16:30] <slangasek> ok
[16:31] <davidbarth> in particular, we've been working with the desktop team on that; more results at the end of this week
[16:31] <davidbarth> with some nice clutter async calls that improve things
[16:31] <davidbarth> plus pitti's awesome patch!
[16:31] <pitti> *beam*
[16:31] <davidbarth> in summary, this is an a3 target
[16:32] <davidbarth> even more now that the desktop team's focus for perf. improvements is moved to the UNE image
[16:32] <davidbarth> back on the desktop for a minute:
[16:32] <davidbarth> dx-lucid-me-menu
[16:32] <davidbarth> dev. plan with work items for a3 and b2
[16:32] <davidbarth> ted is now starting development on it
[16:32] <pitti> I think by and large we are concentrating on the gnome-ish underpinnings, and DX on the new UNE launcher itself
[16:32] <davidbarth> dx-lucid-gtk-improvements
[16:32] <davidbarth> support for indicator object display for dbusmenu
[16:32] <davidbarth> cs-deco focus being worked on with the design team
[16:32] <davidbarth> pitti: right, that's a good summary
[16:33] <davidbarth> and finally the sound menu which has been progressing quite well, but is currently not packaged
[16:34] <davidbarth> we're a bit disapointed not to have this week as initially planned, but we prefer to audit and package it properly
[16:34]  * slangasek nods
[16:34] <davidbarth> and not upload on friday...
[16:34] <davidbarth> that's it for the general report
[16:34] <davidbarth> questions?
[16:34] <slangasek> no other questions from me; others?
[16:35] <slangasek> [TOPIC] Mobile Team
[16:35] <slangasek> davidbarth: thanks
[16:35] <slangasek> asac: go :)
[16:35] <asac> hi
[16:35] <asac> weekly summary:
[16:35] <asac> - uboot: unblocked by using old uboot (2009.01)
[16:35] <asac> - investigating marvel dove (thumb2) hangs: managed to workaround this by not using python!
[16:35] <asac> - ongoing progress on thumb2 package review and ftbfs
[16:35] <asac> - review blueprints and WI for alpha-3
[16:35] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:36] <asac> [LINK] http://macaroni.ubuntu.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html
[16:36] <asac> [LINK] http://macaroni.ubuntu.com/~pitti/workitems/canonical-mobile.html
[16:36] <slangasek> s/macaroni/people/
[16:36] <asac> will refrain to post the info on the status page ;)
[16:37] <asac> ok. didnt know about that alias
[16:37] <asac> thx
[16:37] <pitti> it's not an alias
[16:37] <asac> not?
[16:37] <pitti> the stuff moved to people
[16:37] <pitti> see platform mail
[16:37] <asac> the charts look similar ;)
[16:37] <asac> ok
[16:37] <pitti> yes, it's running in parallel still
[16:37] <pitti> for people who don't read the announcement fast enough :-P
[16:37]  * pitti hugs asac, no worries
[16:37] <lool> http://people.canonical.com/~pitti/workitems/canonical-mobile.html
[16:37] <ogra> what announcement ?
[16:38] <ogra> :P
[16:38] <slangasek> asac: anything from the status report that needs highlighted, that you need input on from other teams?
[16:38] <asac> in the blueprint section i gave an overview of the essential and high prio blueprints
[16:39] <asac> i dont think so ... the dominating issue is still that dove images are hanging ... but
[16:39] <asac> the fact that we can workaround and get a working desktop by not using python, gives me hope
[16:39] <slangasek> asac: mobile-lucid-arm-lightweightbrowser didn't show any change in WI status as of this morning; did the benchmark results come in this week as expected?
[16:39] <asac> i discussed this with doko already
[16:39] <ogra> and the fact that python wasnt rebuilt yet
[16:40] <asac> slangasek: the benchmarking became more tricky ... we are waiting on mozilla input before we can publish those
[16:40] <asac> also the tool ARM uses doesnt even allow the publishing of the results :( ... so we are falling back to javascript testing and startup time... but mozilla asked for a chance to help tuning
[16:41] <asac> we have a meeting early next week
[16:41] <slangasek> speaking of python not being rebuilt, how far out are we from scheduling rebuilds?
[16:41] <slangasek> asac: ah, ok
[16:42] <ogra> didnt we say we'll wait until after DIF ?
[16:42] <asac> we dont get much rebuilds automatically anymore
[16:42] <ogra> (with rebuilds)
[16:42] <asac> the manual rebuild is scheduled for DIF
[16:42] <ogra> right
[16:42] <asac> howver, we want to have the dove issue sorted
[16:42] <asac> because if thats really thumb2 and we cannot workaround we have to reconsider everything
[16:42] <slangasek> you have the list of packages that will need rebuilt, and waiting until DIF looks reasonble in terms of timing?
[16:43] <asac> but we are not that far yet. marvell is working with our kernel peer ... we are trying etc.
[16:43] <asac> slangasek: i would say we could start if there wasnt the uncertainty about thumb2 on dove :/
[16:43] <asac> start doing the manual rebuilds that is
[16:44] <asac> also i think doko wanted to do a lib rebuild and i think he also targetted the DIF for that
[16:44] <asac> so we dont do it twice.
[16:44] <slangasek> oh, you're suspecting that *using* thumb2 is causing problems?  Even though the hangs are in python, which isn't using thumb2 yet?
[16:44] <slangasek> what is doko rebuilding libs for?
[16:45] <asac> slangasek: there was a bug in the symbol generation i think and we suffer from performance issues due to that
[16:45] <asac> dont have the details
[16:45] <slangasek> ok
[16:45] <pitti> wrt rebuilds, we also still need to coordinate some transitions for obsolete libraries; perhaps that will also catch a few of those
[16:45] <asac> can get that to you
[16:45] <asac> (but doko is on holiday till mid next week afail)
[16:46] <asac> slangasek: so we know that there is a silicon bug in dove for thumb2 ... however, personally, i dont think that necessarily the main problem we are seeing
[16:46] <slangasek> ok
[16:46] <slangasek> no more questions here; anything else on mobile?
[16:46] <asac> especially since not using pytyhon gives us a working desktop ... we are trying to get new boards that have that fixed
[16:46] <asac> to check that etc.
[16:47] <slangasek> [TOPIC] Server Team
[16:47] <slangasek> asac, ogra: thanks
[16:47] <ttx> o/
[16:47] <ogra> thanks
[16:47] <slangasek> ttx: 'lo
[16:47] <asac> thanks
[16:48] <ttx> Status was updated at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:48] <ttx> Alpha3-targeted bugs:
[16:49] <ttx> I indecated progress on all the MIR bugs, I think they are in good shape now, just takes some time to finalize the process
[16:49] <ttx> bug 503180 should see progress next week when Dustin comes back from upside-down-land
[16:49] <ttx> Bugs affecting us in other teams:
[16:50] <ttx> there is some discussion around the fix for bug 494565
[16:50] <slangasek> I'm surprised at how long some of those MIRs are taking; even irqbalance could be seeded on server while the discussion of whether to include it on server continues, couldn't it?
[16:50] <ttx> slangasek: yes, I think Chuck has been waiting the answer to see where he should seed it
[16:51] <lool> The MIR is granted though
[16:51] <ttx> yes, it's almost finished [tm]
[16:51] <lool> (Since December along libcap-ng)
[16:51] <ttx> So there is a -devel thread around bug 494565
[16:51] <slangasek> ttx: I don't see any reason not to seed it on server, and change it later if appropriate
[16:52] <ttx> slangasek: ok, will communicate that downstream
[16:53] <ttx> The discussion is about potential drawbacks in generally building some features inkernel rather than inmodule
[16:53]  * slangasek nods
[16:53] <ttx> We need them for -virtual only... but subflavour game means it ends up in -server and -generic-pae as well
[16:54] <ttx> At that point, I'm not sure the feature is worth the risk... so it should either be a full flavor or the feature should be dropped
[16:54] <ttx> But I can be convinced otherwise, if everyone thinks it's safe :)
[16:54] <ttx> Moving on to specs...
[16:54] <slangasek> best to let that discussion run its course on the list, I think, rather than rehashing it here
[16:54] <ttx> yep
[16:55] <ttx> The prio High < 25% ones
[16:55] <ttx> server-lucid-apport-hooks is at 22%, but work items also include targets of opportunity
[16:55] <ttx> so it's actually pretty advanced
[16:56] <ttx> server-lucid-canonical-application-support: that's the MIR things we already discussed
[16:56] <ttx> 20%, should see some advances today
[16:56] <ttx> server-lucid-seeds: 13%, the remaining few work items are more to investigate what pulls some packages in main while we planned to demote them
[16:57] <ttx> server-lucid-uec-testing: 0%, mathiaz just got access to the test infrastructure, we should see good progress on this one next week
[16:57] <ttx> server-lucid-ec2-config: 0%, should be at 50% at the end of the day (only 2 work items in alpha3)
[16:58] <ttx> server-lucid-ec2-boothooks: 0%, blocked by the work on ec2-config, should see some significant progress by next week
[16:58] <ttx> For other specs, please see http://people.canonical.com/~pitti/workitems/canonical-server-lucid-alpha-3.html
[16:58] <slangasek> all sounds good
[16:58] <ttx> which also shows or trands line
[16:58] <ttx> trends, even
[16:59] <ttx> questions ?
[16:59] <slangasek> none here
[16:59] <slangasek> anyone else?
[16:59] <slangasek> [TOPIC] Kernel Team
[16:59] <slangasek> ttx: thanks
[16:59] <slangasek> apw: around?
[17:00] <slangasek> ok, I have his report to dump in the event that he isn't
[17:00] <slangasek> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:00] <slangasek> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[17:01] <slangasek> Much of the work pushed out from Alpha-3 is close to done and should be committed by Platform Sprint.  Due to the rejig of the burn down we have gained some hidden tasks and are now above the line.  We will be reviewing this next week to determine if we need to push out any items.
[17:01] <slangasek> We have just uploaded a 2.6.32.4 kernel with i915.powersave disabled.  This has alievated numerous twitching issues as well as suspend/resume hangs on several netbook platforms.
[17:01] <slangasek> EOF
[17:02] <slangasek> apw: 458537 was discussed last week as "the upstream hardware doesn't support this", but the bug state hasn't changed; can you take an action (asynchronously) to follow through on that, and invalidate the bug if that's what's appropriate?
[17:03] <slangasek> any other questions for kernel?
[17:03] <apw> slangasek, ... hi ... yes that one is on my radar
[17:04] <apw> the current states are confused as there seems to be a bug in devicekit-power yet those are won't fix
[17:04] <apw> will get it fixed up
[17:04] <slangasek> thanks
[17:04] <slangasek> [ACTION] apw to fix up state of bug #458537 to reflect reality
[17:04] <slangasek> [TOPIC] Security Team
[17:05] <slangasek> jdstrand: your agenda section is empty; entertain us with some a capella improv?
[17:05] <jdstrand> o/
[17:05] <jdstrand> heh
[17:05] <jdstrand> yeah, well, alls quiet on the development front
[17:05] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:05] <jdstrand> we are slowly chipping away at stuff. I think kees was the only one to get to any bp items this week
[17:06] <jdstrand> that said, the burndown still shows us as on track
[17:06] <slangasek> great :)
[17:06] <jdstrand> I think that is pretty much it for us, unless people have questions
[17:07] <slangasek> no questions here; others?
[17:07] <slangasek> [TOPIC] Foundations Team
[17:07] <slangasek> jdstrand: thanks
[17:07] <lool> https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:07] <lool> A2 leftovers:
[17:07] <lool> foundations-lucid-gfxboot-update moved to A3; I understand this is still pendin gsome input from DX
[17:07] <jdstrand> sure
[17:07] <lool> foundations-lucid-boot-recovery > done (lp #505887 unblocked)
[17:07] <lool> A3:
[17:07] <lool> http://people.canonical.com/~pitti/workitems/canonical-foundations-lucid-alpha-3.html
[17:07] <lool> foundations-lucid-reliable-device-id-in-grub: good progress from cjwatson
[17:07] <lool> foundations-lucid-index-based-downloads-client, foundations-lucid-software-center-repository-based-index: lots of work from mvo and tremolux on software-center this week
[17:07] <lool> foundations-lucid-better-archive-crawler: good progress last week; IS dependency discovered for changelogs.u.c and unblocked
[17:07] <lool> foundations-lucid-local-repo-support: some progress by mvo this week
[17:07] <lool> foundations-lucid-support-timeframe-information: good progress by mvo last week; extended for armel/regular arches; probably relates to cjwatson's documentation of support of ports vs. archive arches
[17:07] <lool> foundations-lucid-jockey-support-in-ubiquity: ev started looking into this last week
[17:07] <lool> foundations-lucid-lts-upgrades: good progress by mvo last week; discovered some minor things to fixup (e.g. /boot disk size calculation)
[17:07] <lool> foundations-lucid-oem-config: ev implemented hostname support in oem-config
[17:08] <lool> foundations-lucid-laptop-mode-tools-integration: ubuntu-laptop-mode-tools package is in
[17:08] <lool> (done with dump)
[17:08] <lool> Actually forgot:
[17:08] <lool> foundations-lucid-release-collaboration-with-debian: python done
[17:08] <robbiew> \o/
[17:08] <lool> NB: no update on foundations-lucid-pre-desktop-lucid-startup-speed cause Scott was on leave + conference
[17:09] <robbiew> any idea why http://people.canonical.com/~scott/daily-installer/ has stopped updating?
[17:10] <lool> Perhaps he is traveling with the machine generating these?
[17:10] <slangasek> lool: er, what's this status on foundations-lucid-laptop-mode-tools-integration?  there's no ubuntu-laptop-mode-tools package described in the spec/blueprint
[17:10] <slangasek> (nor do I see this package in the archive)
[17:10] <robbiew> lool: no...they sit at home
[17:10] <cjwatson> the new people.canonical.com server requires explicit confirmation from IS for every authorized_keys entry
[17:10] <lool> slangasek: I've seen a new ubuntu-laptop-mode package appear and thought it was related
[17:10] <cjwatson> or at least to permit a user to have working authorized_keys
[17:11] <slangasek> lool: I don't see a package by that name either :)
[17:11] <pitti> robbiew: perhaps Scott pulled out the power when he left for LCA?
[17:11] <cjwatson> since Scott's been travelling, he hasn't been in the office at the same time as the bulk of IS in order to get that reauthorised
[17:11] <lool> My mirror has it for some reason
[17:11] <pitti> aah
[17:11] <robbiew> cjwatson: ah, ack
[17:11] <cjwatson> (plus there was some installer breakage)
[17:11] <robbiew> heh
[17:11] <pitti> http://people.canonical.com/~pitti/bootcharts/ FTR
[17:11] <pitti> there are some current ones
[17:12] <lool> slangasek: http://ports.ubuntu.com/ubuntu-ports/pool/universe/u/ubuntu-laptop-mode/
[17:12] <lool> Sorry if that's an obsolete thing which only I am seeing
[17:12] <cjwatson> that hasn't changed since hardy
[17:12] <slangasek> robbiew, lool: daily-installer stopped updating because he had a failed install that apparently blocks him from further testing until a manual reset
[17:12] <lool> I don't understand why I saw it appear then; sorry, my bad
[17:12] <lool> Must be some local bug I have
[17:12] <robbiew> slangasek: ok, thanks
[17:13] <cjwatson> actually, it seems to have been removed in lucid
[17:13] <cjwatson> maybe that's what you saw
[17:13] <slangasek> cjwatson: oh, the authorized_keys thing is the current problem for that page? n/m then
[17:13] <cjwatson> I suspect there are multiple problems, best resolved once Scott returns
[17:13]  * slangasek nods
[17:13] <lool> cjwatson: Ah I know what happened, it's due to adding/removing my mirror and hte package being removed between mirror updates
[17:14] <lool> Ok; I'll shut up now  :)
[17:14] <slangasek> anyway, until we get plymouth back out of initramfs it's hard to draw any real conclusions about the boot speed in the areas where it currently counts most
[17:14] <pitti> in the meantime, if anyone needs something tested on the mini, please ping me or seb128
[17:14] <pitti> we both have one as a test rig
[17:15] <slangasek> lool: I guess you've reported on those specs where there was progress; what about the ones where there hasn't been progress (which is more likely to be what needs attention)?
[17:15] <JFo> "bcmwl (Ubuntu)":[]
[17:15] <JFo> yes?
[17:16] <JFo> or does it need to be in the linux list?
[17:16] <pitti> JFo: -ECHANNEL?
[17:16] <JFo> sigh
[17:16] <lool> slangasek: I'm afraid I don't have any data on the ones which were not mentionned in activity reports; I guess I should ping the relevant people
[17:16] <JFo> sorry
[17:16] <slangasek> lool: see https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-22 for the list of the high-priority specs that have low completion rates for A3
[17:17] <slangasek> lool: (are you going to be representing Foundations here going forward, is the plan that whoever chairs the Wednesday meeting represents?)
[17:18] <lool> I don't know
[17:18] <cjwatson> I asked lool today on the basis that he'd done Wednesday, although I wasn't intending for that to be a permanent arrangement
[17:18] <slangasek> ok :)
[17:18] <cjwatson> I'm just having some trouble carving out time right now, but this is temporary :-(
[17:18] <cjwatson> so sorry about the short-notice switch
[17:18] <slangasek> any other questions for Foundations?
[17:19] <cjwatson> oem-dvd-iso is my biggest worry right now since it's basically not started, but I think we have time
[17:19]  * slangasek nods
[17:20] <slangasek> [TOPIC] MOTU
[17:20] <slangasek> lool, cjwatson: thanks
[17:20] <slangasek> ScottK: are we throwing out binaries yet? :)
[17:20] <ScottK> slangasek: No.  I wrote the person that was working on that and didn't hear back (he had some health issues before).  I think it's time to find a new victim.
[17:21] <slangasek> you'll send out an RFV as appropriate, then?
[17:21] <ScottK> Unfortunately a side effect of fixing Debian release coordination - Python is I'm now co-maintainer, so still no time.
[17:21] <ScottK> Yes.
[17:21] <ScottK> I do want to bring up a new concern
[17:22] <ScottK> As I wrote to ubuntu-devel last night, I'm worried about the impact of dropping xulrunner
[17:22] <ScottK> asac may have a solid plan for getting rid of anything we can support, but I think we need some coordination around this.
[17:23] <ScottK> I originally got fired up over this last night when there was a casual mention on IRC that "We're dropping xulrunner to Universe."
[17:23] <slangasek> What coordination do you have in mind?  Is there more to it than dropping those packages that won't be supportable?
[17:24] <ScottK> Someone needs to figure out what those are, announce the plan, and track status.
[17:24] <slangasek> ok
[17:25] <slangasek> asac: is someone handling this from the mozilla team?
[17:25] <ScottK> The spec as currently drafted seems ambiguous about the fate of xulrenner
[17:25] <ScottK> renner/runner
[17:25] <ogra> ScottK, german/english ... same word ;)
[17:25] <ScottK> Heh
[17:26] <slangasek> rennt xul rennt
[17:26] <ScottK> If I get the action it'll be to pipe the output of reverse-build-depends into a stack of removal bugs.
[17:26] <ScottK> If someone wants a more nuanced result, they need to step up.
[17:26] <asac> slangasek: its part of the new support-model spec
[17:26] <asac> ScottK: you were even in the UDS session, right?
[17:27] <ScottK> asac: I was.  This is why I was suprised last night when there was discussion of leaving xulrunner in Universe.
[17:27] <asac> so i dont think its realisitic to get rid of all xulrunner rdepends in universe
[17:27] <ScottK> I don't think we have a choice.
[17:27] <ScottK> Xulrunner in Universe is completely unsupportable for an LTS.
[17:27] <asac> so plan is to check what apps are exposed to insecure content and get rid of those
[17:28] <ScottK> And then consider it OK to leave Xulrunner unmaintained?
[17:28] <asac> what doesn unmaintained mean?
[17:28] <ScottK> I thought the plan was to pitch out apps that couldn't be ported to the newer releases.
[17:28] <ScottK> asac: Look at the history of the current xulrunner (not 1.9.1) package.
[17:29] <asac> right. thats the idea
[17:29] <ScottK> OK. Maybe it's just me, but I think you just told me two opposite things are the plan.
[17:29] <asac> first step: get into universe
[17:30] <asac> second step, get rid of everything that cannot be forward ported
[17:30] <slangasek> "what apps are exposed to insecure content" seems orthogonal to "what apps won't be forward-portable to new xulrunner versions"
[17:30] <asac> but in any case xulrunner cannot be removed completely
[17:30] <slangasek> the latter doesn't seem to be mentioned in the workitems for https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-new-firefox-support-model
[17:30] <asac> thats my main point
[17:30] <ScottK> slangasek: For me the opposite part was are we removing xulrunner.
[17:30] <ScottK> asac: Why not?
[17:31] <asac> that would mean we also dump applications that are forward portable
[17:31] <asac> which would be extreme imo
[17:31] <ScottK> That's the part I don't understand
[17:31] <asac> lets move that offline and
[17:31] <asac> maybe present results next week
[17:31] <ScottK> OK.
[17:32] <ScottK> slangasek: I think we need an action here.
[17:32] <slangasek> what is the action?
[17:32] <slangasek> further discussion?
[17:33] <ScottK> For asac and I to review the plan and present the resolution to the release team.
[17:33] <slangasek> [ACTION] asac and ScottK to review the plan for xulrunner demotion and present the resolution at the next meeting
[17:33] <ScottK> Thanks.
[17:33] <slangasek> sure
[17:33] <slangasek> anything else on the MOTU front?
[17:33] <ScottK> Less urgent, but still a concern is merging.
[17:34] <ScottK> We're a bit stuck between MoM being dead and the new UDD way of doing things not being mature.
[17:34] <ScottK> I don't have data in front of me, but I have a concern stuff is getting left behind.
[17:34] <slangasek> there were some problems with bzr branches being out of date; are those resolved now?
[17:34] <ScottK> Some are.
[17:35] <ScottK> The tools are also signifcantly more complex and so there's learning curve.
[17:35] <ScottK> This hits us in Universe where it's a lot of more casual contributors.
[17:35] <ScottK> There is work planned to simplfiy things in the long run, but I don't know what isn't getting done in the meantime.
[17:36] <ScottK> This isn't anything other than vague uneasyness at this point.
[17:36] <slangasek> I guess http://people.ubuntuwire.com/~lucas/merges.html doesn't give us a good overview of that, on account of not including age info?
[17:36] <ScottK> It doesn't.
[17:36] <slangasek> maybe there's a way lucas could add that in
[17:37] <slangasek> over time though, so perhaps we should take this offline for further discussion
[17:37] <cjwatson> I've added a foundations sprint agenda item for that
[17:37] <ScottK> Lucas has made it pretty clear he's gone as far as he has time.
[17:37] <ScottK> He's at the patches welcome stage.
[17:37] <cjwatson> for first week in Feb
[17:37] <ScottK> cjwatson: Cool.
[17:37] <slangasek> ok
[17:37] <ScottK> I think that's all I have.
[17:37] <slangasek> ScottK: if you have further suggestions, do you want to get them to either cjwatson or myself so we make sure we look at them that week?
[17:38] <ScottK> slangasek: OK.
[17:38] <ScottK> Will do.
[17:38] <slangasek> thanks
[17:38] <cjwatson> I honestly think we should just revive and fix MoM for now
[17:38] <ScottK> I'm all for that.
[17:38] <ScottK> It just needs someone to do it.
[17:38] <slangasek> I agree, but haven't had a chance to step up on that
[17:39] <slangasek> [TOPIC] AOB
[17:39] <slangasek> anything else that needs mentioning?
[17:39] <ScottK> slangasek: So add that one (revive MoM) to the list of further suggestions ...
[17:39] <slangasek> 8.04.4 next week; ISO testing is ongoing, final SRUs are being validated
[17:39] <slangasek> ScottK: ack
[17:39] <slangasek> fader_: 8.04.4 hw cert coming along?  No results yet at http://people.canonical.com/~fader/sru-testing/8.04.4.html
[17:40] <fader_> slangasek: I'm running the tests as we speak
[17:40] <slangasek> yay
[17:40] <slangasek> #endmeeting
[17:40] <lool> slangasek: Thanks!
[17:40] <slangasek> thanks, all
[17:40] <fader_> I should have preliminary results this afternoon, but there will likely be a few that get missed and still need tests
[17:40] <slangasek> fader_: sounds reasonble, schedule-wise
[17:41] <fader_> slangasek: cool, I'll drop you a line when I post what I have this afternoon
[17:41] <slangasek> thanks
[17:41] <pitti> thanks all
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:40] <nigel_nb> !ops
[22:40] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <hygcewpb> Your machine has been infected by the recent spam attacks - visit http://www2.freenode.pl/ for a quick and easy solution!
[22:41] <nigel_nb> PLEASE DONT CLICK!
[22:41] <nigel_nb> thanks tsimpson :)