[00:08] <Linuxian> hello
[00:09] <cjohnston> hello Linuxian
[00:09] <Claudinux> Linuxian, hi
[15:55]  * slangasek waves
[15:56] <jdstrand> o/
[15:56] <ogra> moop
[16:00] <slangasek> #startmeeting
[16:00] <cjwatson> hi
[16:00] <MootBot> Meeting started at 10:00. The chair is slangasek.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <asac>  o/
[16:01] <pitti> o/
[16:01] <ttx> o/
[16:01]  * marjo waves
[16:01] <davidbarth> o/ too
[16:01] <slangasek> Riddell, sistpoty|work, apw: ping
[16:02] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-12
[16:02]  * apw waves nochalently
[16:02] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-02-12
[16:02] <slangasek> [TOPIC] Actions from previous meetings
[16:02] <MootBot> New Topic:  Actions from previous meetings
[16:02] <slangasek>   * asac and ScottK to review the plan for xulrunner demotion and present the resolution at the next meeting
[16:02] <slangasek>   * slangasek to poke priorities of hw testing bugs (DONE)
[16:02] <slangasek>   * pitti to triage bug #506816 to see if it's a dkms bug (DONE)
[16:02] <slangasek> asac: what's the status here?
[16:02] <asac> i havent talked to him. but after reviewing the list of what needs xul in main i am confident that we will have to keep it in main even
[16:03] <slangasek> hmm
[16:03] <asac> so what we do is we treat main and universe the same.
[16:03] <asac> e.g. go through the list and dump everything that we cant commit to support
[16:04] <slangasek> well, ok
[16:05] <slangasek> nothing for it, I suppose
[16:05] <asac> if we could get rid of couchdb things would be better ;)
[16:05] <slangasek> heh
[16:05] <slangasek> [TOPIC] Server Team
[16:05] <MootBot> New Topic:  Server Team
[16:06] <ttx> o/
[16:07] <ttx> Status at: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <ttx> Alpha3 milestoned bugs:
[16:07] <ttx> https://bugs.launchpad.net/bugs/492365
[16:07] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:07] <ttx> done now
[16:07] <ttx> next one was also very recently closed
[16:08] <ttx> That leaves us with https://bugs.launchpad.net/bugs/515812
[16:08] <ttx> Which I'm working on right now, setting Inprogress to reflect that
[16:08] <ttx> I'm blocking on my test infra right now
[16:09] <ttx> If I can't get past it, I'll just upload Monday and test with the archive :)
[16:09] <ttx> Alpha3 status/progress at:
[16:09] <ttx> http://people.canonical.com/~pitti/workitems/canonical-server-lucid-alpha-3.html
[16:09] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-server-lucid-alpha-3.html
[16:10] <ttx> Only 2 High/Essential specs at < 80% completion
[16:10] <ttx> server-lucid-uec-testing (50%): Most remaining work items are about exercising tests, can be completed after FF
[16:11] <ttx>  server-lucid-seeds (50%): Pending redhat-cluster-suite and ctdb discussions, my understanding is that demotions can be finalized after FF as well.
[16:11] <ttx> Bugs in other teams affecting us:
[16:11] <ttx> https://bugs.launchpad.net/bugs/506297
[16:11] <slangasek> (last-minute shuffle of the agenda order, asac needs to get out of the meeting early today)
[16:11] <ttx> This one raises the interesting question of the necessity of plymouth on servers, if it triggers some instability
[16:12] <slangasek> er, which I answered in the bug log
[16:12] <ttx> slangasek: yes, I saw that :)
[16:13] <ttx> slangasek: do you expect to fix that issue for alpha3 ?
[16:13] <ttx> (you as in "Foundations team")
[16:14] <slangasek> it's not really about the pretty splash - we could even disable that for server if that's deemed appropriate; the real issue is having a common interface for boot-time processes to talk to... carrying lots of extra code in all the other packages to work around this would be a fail
[16:15] <slangasek> ttx: Keybuk thinks we need to be waiting for a new upstream code drop that changes a lot of code, which either will fix it or will change so much that we should wait for it to land before hacking on it; I don't have a timeline from him for this yet
[16:15] <ttx> slangasek: right, I think that would be a fallback option, better try to fix the bugs
[16:15] <ttx> slangasek: is it reasonable to make a decision on that by beta1 ?
[16:15] <Keybuk> slangasek: 5-10 days
[16:15] <slangasek> there you go :)
[16:16] <ttx> Keybuk: thanks !
[16:16] <slangasek> so if it's not fixed for alpha-3, it should definitely be fixed for beta-1
[16:16] <Keybuk> exactly
[16:16] <ttx> That's all from me, questions ?
[16:17] <slangasek> none here, anyone else?
[16:17] <Keybuk> ttx: my understanding is that there *should* be a graphical screen for server
[16:17] <slangasek> [TOPIC] Mobile Team
[16:17] <MootBot> New Topic:  Mobile Team
[16:17] <Keybuk> just that when boot is done, it should show the getty
[16:17] <asac> cool. thanks a lot slangasek
[16:17] <Keybuk> is that right?
[16:17] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:17] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:18] <asac> so we have switched to UNE ... and have the 2d launcher now!
[16:18] <ogra> \o/
[16:18] <ogra> its so sexy !
[16:18] <ttx> Keybuk: yes, that's what the bug is about. But I'd rather say that there *could* be a graphical screen for server
[16:18] <asac> very nice expereience i suggest anyone with arm boards to try that ;)
[16:18] <ogra> ++
[16:18] <cjwatson> ttx: the default will be one or the other
[16:18] <ttx> Keybuk: I don't mind it if it works, but I don't mind if there isn't one either
[16:18] <asac> another really good news is that we managed to mitigate the doomy thumb2 on dove issue
[16:19] <asac> using a kernel patch and swapping hardware ... that finally unblocks the thumb2 rebuild spec
[16:19] <ogra> by switching to new silicon :)
[16:19] <asac> and continue with the thumb2 porting
[16:20] <asac> also we unbroke mono and now have good images for dove and imx51 (last i looked)
[16:20] <slangasek> ah, great!
[16:20] <ogra> todays was fine :)
[16:20] <asac> please dont upload anything like mono and openoffice till alpha-3 is over ;)... thanks
[16:20] <ogra> heh
[16:21] <asac> on the bug front we got a bunch of bugs fixed ...
[16:21]  * ogra always thought he was the only one saying that :)
[16:21] <asac> i made the important thumb2 bugs release critical now (as you can see on the agenda)
[16:21] <asac> we are organizing mini sprints now to get that list to zero ... then we will continue and work on the not-so-serious thumb2 issues identified
[16:21]  * ogra notes that bug 457878 isnt on the report (it should be)
[16:22] <asac> maybe the link again
[16:22] <ogra> kernel team is actively working on it
[16:22] <asac> [LINK] https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList
[16:22] <MootBot> LINK received:  https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList
[16:22] <asac> ogra: let me check
[16:22] <asac> ogra: feel free to target for release on your own next time ;)
[16:23] <ogra> its milestoned, but not targeted :/
[16:23] <asac> i will add that to the wiki after meeting. thanks
[16:23] <slangasek> asac: now, what about the lightweight browser decision?
[16:24] <asac> we are waiting on a reply from chromium devs about their release/security update model ...
[16:24] <asac> e.g. we would use it i think if we get green light from security team
[16:24] <slangasek> ok
[16:24] <asac> but after talking to kees ... he feels not good about that unless we figure out how that can be supported decently
[16:25] <slangasek> who's responsible for following up with chromium upstream?  mobile or security?
[16:25] <asac> me ... but i think its a good idea to keep security in the loop
[16:25]  * slangasek nods
[16:25] <asac> will do that from now on
[16:26] <slangasek> it's starting to get late for switching the default browser (MIRs, FF, etc) - can we expect some progress on this by next week?
[16:26] <marjo> slangasek: agree
[16:26] <asac> slangasek: yes. i try
[16:26] <pitti> is chromium really that much more "lightweight" than firefox, which would justify the enormous commitment?
[16:26] <asac> slangasek: note though that its not a default switch on all images
[16:26] <slangasek> asac: that changes nothing :)
[16:27] <pitti> (it's no different from firefox here, but then that's just my crappy box)
[16:27] <asac> pitti: it is much faster
[16:27] <ogra> pitti, it scrolls without stuttering in frambuffer and starts up a lot faster
[16:27] <pitti> ogra: ah, I wouldn't notice scrolling speed
[16:27] <ogra> remember we dont have xservers on armel
[16:27] <pitti> startup is just as slooow as ffox here
[16:27] <pitti> anyway, you guys measure it on the relevant hardware
[16:27] <pitti> so ignore me
[16:28] <asac> so yes. lets say we need to see good progress by next week to pursue this idea
[16:28] <slangasek> anything else on mobile?
[16:28] <asac> not from me
[16:28] <slangasek> [TOPIC] Kernel Team
[16:28] <MootBot> New Topic:  Kernel Team
[16:28] <slangasek> asac, ogra: thanks
[16:28] <asac> thanks
[16:28]  * ogra thakls the installer team for help on oem-config 
[16:28] <slangasek> apw: hi
[16:28] <ogra> *thanks
[16:28] <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 60% and are on target to complete them.  We remain above the line on our burn-down chart (at the third URL below), but we made significant progress last week at Sprint towards hitting that target:
[16:28] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:28] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:28] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:28] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:28] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-3
[16:28] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:28] <apw> We reviewed suspend/resume strategy last week, we now have additional diagnostics patches in testing to aid diagnosability of suspend issues, we have also put a triage and diagnosis plan in place to aid characterisation and detection of common faults.  The ubuntu delta tasks are progressing with the discussed patch changes being applied and uploaded for testing.  Of the three arm bugs called out, one is believed fixed, the second has patches which
[16:28] <apw>  are under review, and the third remains under investigation.
[16:28] <apw> Testing of the Nouveau LBM package has been fairly good so far and an updated version has been uploaded and awaits source NEW, userspace bits should already be in place.  The distro kernel is now pulled up to v2.6.32.8 and remains pretty stable in testing.  The mvl-dove branch has been rebased to the distro tip and stabilising patches applied, testing is ongoing.
[16:29] <apw> .. done
[16:31] <slangasek> any questions for kernel?
[16:32] <slangasek> [TOPIC] QA Team
[16:32] <MootBot> New Topic:  QA Team
[16:32] <slangasek> apw: thanks
[16:32] <slangasek> marjo: hi
[16:32] <marjo> HW Testing
[16:32] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:32] <marjo> Netbook:
[16:32] <marjo>    passed:   7 (54%) failed:   3 (23%) untested: 3 (23%)
[16:32] <marjo> Laptop:
[16:32] <marjo>    passed:   23 (92%) failed:    0 ( 0%) untested:  2 ( 8%)
[16:32] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:32] <marjo> Server:
[16:32] <marjo>    passed:   52 (98%) failed:    0 ( 0%) untested:  1 ( 2%)
[16:32] <marjo> Desktop:
[16:32] <marjo>    passed:   12 (100%) failed:    0 (  0%) untested:  0 (  0%)
[16:33] <marjo>    * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:33] <marjo> Still targeting for lucid-alpha-3.
[16:33] <marjo>    * UbuntuSpec:qa-lucid-automated-server-testing
[16:33] <marjo> Alpha-3 work items being transferred to ara and sbeattie from soren.
[16:33] <marjo> On track for alpha-3
[16:34] <marjo> that's all folks from QA team, any questions?
[16:34] <pitti> netbook failure is still due to the same sound card bug?
[16:35] <slangasek> yes
[16:35] <fader_> pitti: probably; I've asked alexmoldovan to gather the info on those bugs
[16:35] <marjo> pitti: we will also file additional bugs today as more analysis is done
[16:35] <fader_> He turned them up yesterday and hasn't yet filed bugs
[16:36] <slangasek> https://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-checkbox-desktop-experience-tests - is that actively under development?  Some of the work items are rather broad ("integrate new tests during the course of the release"), I wonder if this is really on track
[16:36] <marjo> slangasek: yes, just confirmed with cr3 today
[16:36] <marjo> we'll adjust work items to be more precise, if necessary
[16:37] <slangasek> that particular one could probably use some finer-grained detail
[16:37] <marjo> slangasek: agree
[16:37] <slangasek> anything else on QA?
[16:37] <slangasek> [TOPIC] Desktop Team
[16:37] <MootBot> New Topic:  Desktop Team
[16:37] <slangasek> marjo, fader_: thanks
[16:37] <slangasek> pitti: hi
[16:37] <pitti> as usual, our report is on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:37] <pitti> since the last meeting we made great progress on landing specs, and boot speed,
[16:37] <marjo> slangasek: thx!
[16:37] <pitti> see wiki for details
[16:38] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:38] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:38] <pitti> specs which were called out in the invitation:
[16:38] <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; might still be a bit rough for alpha-3, but believed to be fixable for lucid.
[16:38] <pitti> desktop-lucid-xorg-triaging-diagnosis: remaining work is outside the distro around bug management; some bits might get dropped, and until now Bryce worked on more urgent tasks
[16:38] <pitti> (remain targets of opportunity, since investments there will save time later on)
[16:38] <pitti> lucid-ubuntu-one-client-app: Goal of OLS, not desktop team
[16:38] <pitti> but was confirmed to be on track for FF
[16:39] <pitti> (I can't say much about it beyond that, I'm afraid)
[16:39] <pitti> the bug front remains reasonably calm, most important one was a regression due to ATI KMS; still being figured out (details in the wiki report)
[16:39]  * jdstrand hates that bug
[16:40] <pitti> oops, please ignore the "planned intrusive changes for alpha-3" section, it was old; I just removed it from the wiki page
[16:40] <slangasek> that's bug #507148, I guess?
[16:40] <pitti> right
[16:40] <jdstrand> yeah
[16:40] <pitti> this will probably require a pull of ati/rdm from 2.6.33
[16:40] <jdstrand> btw-- you can see in the bug and upstream report-- still no progress
[16:41] <pitti> or we have to disable KMS on ATI by default
[16:41] <pitti> oh, the Ubuntu bug has a lot of recent action
[16:43] <slangasek> is there any more news on https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-openoffice?  (spec says "there is currently not a roadmap")
[16:44] <pitti> 3.2.0 is in lucid right now
[16:44] <pitti> but beyond that it depends on upstream whether .1 lands on time
[16:44] <slangasek> yes, but the spec says 3.2.1, and says it's not due out until March-ish
[16:44] <slangasek> (in fact, we only have 3.2.0 rc4 in lucid...)
[16:45] <pitti> I don't know more precise dates right now, but I'm happy to discuss with Chris
[16:46] <slangasek> I think it would be good to pin that down more precisely, yes
[16:46] <slangasek> anything else for desktop?
[16:47] <jdstrand> pitti, slangasek: fyi-- I'm very keen to get that radeon bug fixed. I have several people who have this card depending on me to upgrade their machines to Lucid
[16:47] <pitti> no Kubuntu report this week, Riddell is on holiday
[16:47] <jdstrand> pitti, slangasek: I'm affected too, so it is easy for me to test things
[16:48] <pitti> it seems the kernel team has backported much of the stack and is calling to test them
[16:48] <pitti> but it's certainly not an easy backport
[16:48] <apw> we have a small backport of 4 patches which i am told stop it crashing
[16:48] <jdstrand> I've tested everything they gave me so far-- no difference afaics
[16:48] <apw> in nomodeset mode
[16:49] <jdstrand> apw: with or without compiz?
[16:49] <slangasek> isn't that bug report specifically about KMS?
[16:49] <apw> which would the lower risk option i presume...  i've note reviewed them yet
[16:49] <jdstrand> slangasek: I think they are hoping to have a fallback
[16:49] <pitti> it was said to not overrun memory when disabling modeset, yes
[16:50] <jdstrand> well, with no KMS, using compiz results in a different problem-- hard lockup (I filed a bug)
[16:50] <slangasek> ah
[16:50] <apw> which presumably you would get with KMS too if it worked
[16:50] <jdstrand> the only working configuration is no KMS, use XAA, do not use compiz and use RenderAccell off
[16:50] <apw> the plans are needing discussion, but the original was to disable cards which do not work with KMS
[16:51] <slangasek> ok, sounds like there's a lot of following up to be done there
[16:51] <apw> the other bug is a plain regression i assume, and we may have fixes for it
[16:51] <slangasek> which I trust jdstrand will help with, since he has motivation :)
[16:51] <jdstrand> apw: compiz with KMS crashes compiz and is bug #507148. compiz without KMS is a lockup (not a memory issue)
[16:52] <apw> can you get me the other bug number too please
[16:52]  * jdstrand looks
[16:53]  * davidbarth waves: DX? while jstrand looks for the bug?
[16:53] <slangasek> jdstrand: when you have it, please follow up with apw as needed
[16:53] <slangasek> [TOPIC] DX Team
[16:53] <jdstrand> apw: there are actually several I've filed: 513950, 513956, 507148
[16:53] <MootBot> New Topic:  DX Team
[16:53] <davidbarth> eh
[16:53] <slangasek> davidbarth: yes :)
[16:53] <slangasek> pitti: thanks
[16:53] <davidbarth> ok, so the report is at https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:54] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:54] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:54] <jdstrand> apw: and one more that only affects notify-osd with XAA: 513968. that is worked around by using RenderAccel off
[16:54] <davidbarth> dx-lucid-application-indicator
[16:54] <davidbarth> big compatibility change last week; allows KDE & Gnome to finally share compatible APIs, namespaces, types, etc.
[16:54] <davidbarth> created some side effects while the different libs & desktops were out-of-sync, should be resolved with the latest kubuntu update as of today
[16:54] <davidbarth> stream of bug reports (and some fixes for them), thanks to the porting effort with app. indicators
[16:55] <jdstrand> apw: also, the upstream bug listed in 507148 has a lot of info
[16:55] <davidbarth> for this blueprint, we are in bug fix mode now
[16:55]  * jdstrand is done
[16:55] <davidbarth> dx-lucid-gtk-improvements
[16:55] <davidbarth> ongoing work on further gtk patches for cs-deco; plan is to release that early next week, before the Thursday upload window
[16:56] <davidbarth> so this one is a bit particular, the cs-deco changes can create some artefacts: layout issues mostly
[16:56] <davidbarth> setting up a test-plan with qa (as planned in the bp, but coming late) to cope for that
[16:57] <davidbarth> the thing we'll be adding early next week is the ability to blacklist apps that have issues, to be able to better control that kind of bugs
[16:57]  * slangasek nods
[16:57] <davidbarth> dx-lucid-sound-indicator
[16:57] <davidbarth> finally in Lucid! please report bugs; known issues (unimplemented: auto-mute detection and automatic switching of default output device)
[16:57] <davidbarth> ("and there was much rejoicing" ;)
[16:58] <davidbarth> dx-lucid-me-menu
[16:58] <davidbarth> landed last week, as part of the Portland sprint; new integration with gwibber mostly, featuring an IDO (IndicatorDisplayObject) entry in the menu
[16:58] <davidbarth> IM integration, same as when integrated in the SessionMenu
[16:58] <davidbarth> will continue integration with the "About Me" feature for A3
[16:58] <davidbarth> and another menu next:
[16:58] <davidbarth> dx-lucid-session-menu
[16:58] <davidbarth> user list and switching feature restored; based on the new API provided by Robert Ancell
[16:59] <davidbarth> so this one should be feature complete now
[16:59] <davidbarth> keeping a wi open for potential integration issues left after that release
[16:59] <davidbarth> and some more:
[16:59] <davidbarth> dx-lucid-notifications
[16:59] <davidbarth> set of former SRU candidates, now merged into trunk
[16:59] <davidbarth> closeNotification API fix remaining
[16:59] <davidbarth> bp should be 100% complete after that
[17:00] <davidbarth> that's it for bp/wi tracking
[17:00] <davidbarth> one bug in the agenda:
[17:00] <davidbarth> 506683: indicator-applet doesn't show menu choices when selected
[17:00] <davidbarth> so this one was meant to be fixed by the big dbusmenu/indicate update of last week; but was not tracked per se
[17:00] <davidbarth> ie, can't 100% say we've closed it
[17:01] <slangasek> I was seeing the bug with some frequency before; I can watch for it and update the bug for next week
[17:01] <davidbarth> will nudge ted on monday specifically, but i haven't spotted occurences of that kind of bug anymore
[17:01] <davidbarth> yes, safe to keep it on the agenda, as it was a tricky race condition
[17:02] <davidbarth> and it took some time and 2 releases for ted to feel better about it
[17:02] <davidbarth> that's it for the report
[17:02] <davidbarth> questions, feel free to ask
[17:02] <slangasek> [ACTION] slangasek to follow up on bug #506683 to verify whether it's reproducible after latest indicator uploads
[17:02] <MootBot> ACTION received:  slangasek to follow up on bug #506683 to verify whether it's reproducible after latest indicator uploads
[17:03] <slangasek> no questions here; anyone else?
[17:03] <davidbarth> i guess we could also try to track the app. indicator porting effort as part of that
[17:03] <slangasek> as part of which?
[17:03] <davidbarth> i haven't looked at the status for the different apps, but the latest status was that it was proceeding well
[17:04] <davidbarth> there is a big list maintained by community; maybe i'll let jono or jorge comment as part of their report
[17:04] <slangasek> the community team doesn't report as part of this meeting?
[17:04] <davidbarth> we're also tracking some libappindicator/dbusmenu bug repotrs that are filed by porters; that's a nice sting to improve that infrastructure
[17:04] <jcastro> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application
[17:05] <jcastro> ^^^ that's the progress of the porting work
[17:05] <davidbarth> jcastro: yes, thanks for the link
[17:06] <slangasek> [LINK] https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application
[17:06] <MootBot> LINK received:  https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=indicator-application
[17:06] <slangasek> how many of these apps are expected to change for lucid?  (Since that's all feature work, and is affected by FF)
[17:07] <davidbarth> as much as possible; knowing that the fallback support mechanism makes safe a safe path
[17:07] <jcastro> everything is on the default desktop has a contractor assigned with the goal of making FF
[17:07] <slangasek> ok
[17:07] <davidbarth> ie, apps that are not ported continue to work with the old systray
[17:08] <jcastro> the universe ones are community opportunities.
[17:08] <davidbarth> right
[17:09] <slangasek> ok - anything else on DX?
[17:09] <davidbarth> slangasek: nope, that's it for me
[17:09] <slangasek> [TOPIC] Foundations Team
[17:09] <MootBot> New Topic:  Foundations Team
[17:09] <slangasek> davidbarth: thanks
[17:09] <slangasek> cjwatson: hi
[17:09] <cjwatson> https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:10] <cjwatson> I've put summaries there of all the specs in the agenda, as well as a few others that have mostly been deferred now
[17:10] <cjwatson> the only ones I'm actively concerned about are the software-center ones, which I think were always likely to run late or have bits deferred
[17:11]  * slangasek nods
[17:11] <cjwatson> slangasek: would appreciate your feedback on the remaining bits of release-collaboration-with-debian, as I'm not very current on that
[17:11] <cjwatson> the rest of pre-desktop-lucid-startup-speed should land next week, subject to fixing this automatic installation bug which I'm going to try to do today; Keybuk says he believes that should get us very close to the 10s targets
[17:12] <cjwatson> *target
[17:12] <slangasek> one of the remaining items there is openoffice.org, which it seems still has some uncertainty on our side; I'll follow up with ccheney today and also check with _rene_
[17:12] <pitti> (FYI, 11.2 s with the rsyslog/dd change done locally)
[17:13] <slangasek> java/X, I'll look at in the next few days as well; perl, we're current with Debian now so that probably just needs the status updated
[17:14] <cjwatson> yeah, I assume the question was whether we were going to remain current ;-)
[17:14] <slangasek> well, there is that. :)
[17:14] <cjwatson> I'm going to be off next week, so am mostly trying to nail down the absolutely vital stuff today, like the gfxboot changes
[17:15] <slangasek> (at the time the question was raised, we were behind Debian by a perl point release)
[17:15] <cjwatson> oh, right, that was never really a big problem
[17:16] <cjwatson> if perl were hard to merge, we'd have somebody permanently assigned to it :)
[17:17] <cjwatson> anyway, nothing else here, unless there are other questions
[17:19] <slangasek> no questions here
[17:19] <slangasek> anyone else?
[17:20] <slangasek> [TOPIC] Security Team
[17:20] <MootBot> New Topic:  Security Team
[17:20] <slangasek> cjwatson: thanks
[17:21] <jdstrand> so, ass always: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <jdstrand> hehe
[17:21] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <jdstrand> s/ass/as/
[17:21] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <jdstrand> We postponed a few medium and lower items before the sprint.
[17:21] <jdstrand> so our burndown overall looks good
[17:21] <jdstrand> for alpha 3 we have http://people.canonical.com/~pitti/workitems/canonical-security-lucid-alpha-3.html
[17:22] <jdstrand> While security-lucid-ufw-devel is targeted for alpha 3 and shown as 17% (5 items left), the reality is that the work is almost done and it just hasn't hit Ubuntu yet. That should be at 100% completion sometime next week when I upload ufw 0.30.
[17:22] <pitti> this graph looks backwards..
[17:22]  * slangasek grins
[17:23] <slangasek> and the burndown line is across the bottom, that's no good :)
[17:23] <jdstrand> that graph never made a lot of sense to me...
[17:23] <jdstrand> but, the Status by specification does...
[17:23] <jdstrand> (which is what I am talking about here :)
[17:24] <jdstrand> beyond that, we have no RC bugs and are on track
[17:24] <slangasek> great to hear
[17:24] <jdstrand> that is it from me
[17:25] <slangasek> any questions for security?
[17:25] <slangasek> [TOPIC] MOTU
[17:25] <MootBot> New Topic:  MOTU
[17:25] <slangasek> jdstrand: thanks
[17:25] <slangasek> sistpoty|work, ScottK: here?
[17:25] <jdstrand> sure :)
[17:26] <ScottK> slangasek: Here, but I'm on travel for work, so I have no idea what's going on in MOTU right now.
[17:26] <slangasek> ok
[17:26] <slangasek> [TOPIC] AOB
[17:26] <ScottK> Just barely managed to be on IRC.
[17:26] <MootBot> New Topic:  AOB
[17:26] <slangasek> anything else to touch on this week?
[17:27] <slangasek> FF is next Thursday, in case anyone didn't notice :)
[17:27] <slangasek> so if you're going to need freeze exceptions, it's not too early to let the release team know
[17:27]  * slangasek raises the gavel in slow motion
[17:28] <slangasek> #endmeeting
[17:28] <MootBot> Meeting finished at 11:28.
[17:28] <slangasek> thanks, folks!
[17:28] <pitti> thanks everyone
[17:40] <sistpoty|work> slangasek: sorry, was afk, had a lengthy debug session with a coworker
[17:41] <slangasek> sistpoty|work: no worries - anything you wanted to share today?
[17:41] <sistpoty|work> slangasek: well, I wanted to raise the question about merging ubuntu-release and motu-release
[17:42] <sistpoty|work> slangasek: and in case we want to do this if we already want to do this for lucid
[17:42] <slangasek> I think it should happen for lucid; I'll follow up to the mailing list thread today
[17:43] <sistpoty|work> slangasek: *nod*, especially since FF is very close
[17:43] <sistpoty|work> thanks!