[15:57] <slangasek> good morning
[15:57]  * fader_ waves.
[15:57] <ttx> slangasek: o/
[15:57]  * fader_ is filling in for marjo today.
[15:59] <ogra> moop
[15:59] <pitti> \o
[16:00] <ScottK> o/
[16:00] <Riddell> hola
[16:01] <asac> o/
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-05
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-05
[16:01] <slangasek> [TOPIC] Actions from previous meetings
[16:01] <MootBot> New Topic:  Actions from previous meetings
[16:01]  * apw appears
[16:01] <slangasek>   * QA Team to retest Kubuntu desktop after ubiquity uploads
[16:01] <slangasek>   * slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:01] <slangasek>   * seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[16:02] <slangasek>   * davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[16:02] <slangasek>   * ScottK, slangasek to review python sync/merge candidates ~Mar 12
[16:02] <fader_> slangasek: Ara has been performing some of the tests of the pairwise testing efforts.  You can check results at:
[16:02] <fader_> http://pairwise.qa.ubuntu.com
[16:02] <MootBot> LINK received:  http://pairwise.qa.ubuntu.com
[16:02] <fader_> As you can see, Kubuntu ubiquity crashes in both i386 & amd64, so we couldn't perform any of tests for Kubuntu fixes, but we could catch some
[16:02] <fader_> new bugs, confirmed others, and we have been communicating those to the installer team.
[16:03] <Riddell> it does?  how do i see that?
[16:03] <fader_> Riddell: The bugs column on the right has links to the relevant bugs in LP
[16:03] <slangasek> bug #532533?
[16:04] <slangasek> (targeted)
[16:04] <pitti> slangasek: outstanding firefox-support-model WI is done
[16:04] <slangasek> pitti: ta
[16:05] <slangasek> ebsroot> still outstanding on my end
[16:05] <pitti> startup speed budget> was quite okay until yesterday, but regressed a bit; was discussed this morning, they are investigating
[16:05] <slangasek> davidbarth: did you have a chance to check where netbook-launcher is on its bootspeed budget?
[16:05] <davidbarth> slangasek: hi; yes
[16:06] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100303-1.png was perfect :)
[16:06] <MootBot> LINK received:  http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100303-1.png was perfect :)
[16:06] <davidbarth> slangasek: unfortunately we don't pass; same as for desktop where gnome-panel and the rest of that inftrastructure slows us down
[16:06] <davidbarth> saw that with seb128 and didrocks and there's not much else we can do at this stage
[16:06] <pitti> yes, desktop is a lost cause due to compiz mainly
[16:07] <pitti> it's 16 s; we can make significant gains by switching to metacity; but it's not on the lucid plan any more
[16:08] <slangasek> yes, we're not concerned with desktop, only with netbook
[16:08] <slangasek> you'd better not be saying that netbook is a lost cause :)
[16:08] <davidbarth> slangasek: didrocks still has a few tricks up his sleeve to get 1s back
[16:08] <pitti> 1s! wow
[16:08] <slangasek> 1s?
[16:09] <pitti> I still know about the background caching in ubiquity (branch merge proposal pending)
[16:09] <apw> 10%
[16:09] <davidbarth> possibly, yes we're still loading some things multiple times and that may help
[16:09] <pitti> that should buy some .3 s
[16:09] <pitti> davidbarth: ah, nice
[16:10] <davidbarth> but to conclude on that, i think that goal should be marked deferred to L+1 due to the infratructure we're still using with that version of the netbook launcher
[16:10] <slangasek> what goal should be marked as deferred?  the bootspeed goal?
[16:11] <cjwatson> I'm going to do the background caching in ubiquity today
[16:12] <cjwatson> or merge didrocks' work anyway
[16:14] <slangasek> ok, I've had it clarified that the netbook-launcher is not being used as the reference for the 10s boot, so I don't think we need to spend more time discussing this
[16:15] <pitti> so, we optimized the startup and GNOME infrastructure, but not gnome-panel/compiz themselves
[16:15]  * slangasek nods
[16:15] <pitti> since they are going to be replaced in 10.10, and bringing them into the budget would mean to rewrite them from scratch
[16:15] <slangasek> [TOPIC] QA Team
[16:15] <MootBot> New Topic:  QA Team
[16:16] <fader_> Hardware testing:
[16:16] <fader_> http://people.canonical.com/~fader/hw-testing/current.html
[16:16] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:16] <fader_> Netbook:
[16:16] <fader_>  passed:   10 (77%)    failed: 1 (8%)   untested: 2 (15%)
[16:16] <fader_> Laptop:
[16:16] <fader_>  passed:   30 (100%)   failed: 0 (0%)   untested: 0 (0%)
[16:16] <fader_> Server:
[16:16] <fader_>  passed:   56 (95%)    failed: 0 (0%)   untested: 3 (5%)
[16:16] <fader_> Desktop:
[16:16] <fader_>  passed:   11 (92%)    failed: 0 (0%)   untested: 1 (8%)
[16:16] <fader_> We have also begun a round of manual tests on the laptops in the lab.
[16:16] <fader_> http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:16] <MootBot> LINK received:  http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:16] <fader_> alexmoldovan has been a rockstar on this, going through and running checkbox interactively on them
[16:16] <fader_> Most of what we're seeing is the network manager applet missing (bug 520589)
[16:16] <fader_> He found some other webcam and audio issues yesterday that we'll make sure to get bugs in for today
[16:16] <fader_> Spec status:
[16:16] <fader_> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:16] <fader_> marjo says "By default, all 10.04-beta1 work items are on-track."
[16:16] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:16] <fader_> cr3 has postponed several items to beta.
[16:16] <fader_> [that's it]
[16:17] <slangasek> bug #520589> er. icon *missing*?
[16:17] <fader_> Oh, I should add we're continuing the manual tests in the lab -- this report represents what has been done so far but there is more to go
[16:18] <fader_> slangasek: He's reporting that most of the systems simply don't have the network manager applet
[16:18] <fader_> Several do, but most do not
[16:18] <slangasek> pitti, davidbarth: do you know what this is about?  is this related to indicator-* support?
[16:19] <slangasek> fader_: testing is with alpha-3 media?
[16:19] <pitti> it's not indicator-ified; I had suspected the new theme, but the bug is much older
[16:19] <pitti> first time I hear about this problem (never saw this), I'll put it on my list to investigate
[16:19] <fader_> slangasek: He was testing with images from yesterday, so post alpha-3 builds by a few days
[16:19] <fader_> There were some troubleshooting steps listed in the bug that I've asked him to take a look at as well
[16:19] <slangasek> [ACTION] pitti to follow up on bug #520589
[16:19] <MootBot> ACTION received:  pitti to follow up on bug #520589
[16:20] <pitti> fader_: so you can replicate this? there's no duplicates or other affected persons
[16:20] <fader_> alexmoldovan: ^^ this was happening repeatably on multiple systems, correct?
[16:21] <pitti> let's discuss in the bug, to not hold up the meeting
[16:21]  * davidbarth reads back
[16:21]  * slangasek nods
[16:21] <fader_> pitti: Sounds good; my plan was to work with him on bugs he's found today
[16:21] <fader_> So we'll be sure to get as much info as possible for that one
[16:23] <slangasek> fader_: is there anything new to report regarding alpha3 tests?  (how are we doing on getting the reported bugs fixed, etc)
[16:23] <fader_> slangasek: Nothing yet, other than it looks like hibernate is working much better now
[16:23] <fader_> alexmoldovan has found some audio and webcam bugs yesterday that we'll file today
[16:23] <fader_> I'll make sure to get you the bug numbers
[16:24] <slangasek> fader_: sorry, I meant the report that rounds up all the ISO testing bugs
[16:24] <fader_> slangasek: Ah, sorry.  I don't have any info on that one, so I think we'll have to ask marjo when he's back
[16:24] <slangasek> as for http://people.canonical.com/~fader/milestones/lucid/alpha3.html, that lists bug #520589 for a number of units - did you say this is testing with daily images instead of the alpha-3 images?  I'm not sure that's appropriate
[16:25] <fader_> slangasek: Yes, it was with post-A3.  If you'd prefer we use A3 specifically for this I'd be happy to switch to that
[16:25] <slangasek> fader_: I don't see the point of doing extensive "alpha 3" testing with a random daily
[16:26] <slangasek> since apparently you're hitting random desktop bugs by doing this :)
[16:26] <fader_> slangasek: The goal here was to get manual testing more than a3-specific testing
[16:26] <fader_> slangasek: But you're right that it probably makes more sense to stick with one consistent image
[16:27] <fader_> We plan to do another round of manual testing during beta; for that I'll make sure we use the 'golden' beta image from the start so we aren't getting a random daily
[16:28] <slangasek> fader_: 530380 is targeted to beta-1 but has no assignee; who should take this? cr3?
[16:28] <slangasek> bug #530380
[16:28] <cr3> slangasek: it's on my radar, I'll assign it to myself
[16:28] <slangasek> thanks
[16:29] <slangasek> anything else on QA?
[16:29] <cr3> slangasek: I'm waiting for a branch to land before tackling it
[16:29] <fader_> slangasek: Nothing else from me
[16:29] <slangasek> [TOPIC] Server Team
[16:29] <MootBot> New Topic:  Server Team
[16:29] <slangasek> fader_: thanks
[16:29] <slangasek> ttx: hi
[16:29] <ttx> o/
[16:29] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <ttx> Updated a couple minutes ago for freshness
[16:30] <jiboumans> o/
[16:30] <ttx> Beta1-milestoned bugs:
[16:30] <ttx> Only three left
[16:30] <ttx> bug 499389, assigned to zul
[16:30] <slangasek> (the UHT server report)
[16:30] <ttx> bug 519513, assigned to kirkland, in progress with upstream
[16:31] <ttx> and the munin MIR dependency, bug 526480
[16:31] <ttx> this one is blocked on MIR team review, assigned to asac
[16:31] <asac> i am downloading it now
[16:31] <ttx> asac: thanks !
[16:31] <asac> sorry
[16:31] <slangasek> ok, great :)
[16:31] <ttx> Beta1 specs progress :
[16:31] <ttx> High/Essential specs at < 40% completion
[16:31] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-ec2-ebsroot
[16:32] <ttx> 27% -- Good progress, test deliverables should be generated soon
[16:32] <ttx> soon as in "today".
[16:32] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-uec-testing
[16:32] <ttx> 29% -- Good progress, not impacted by Beta1Freeze or release process
[16:32] <ttx> some issues with the multi-network setup
[16:33] <ttx> in a UEC configuration that's not so easy to test at home.
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-daily-vcs
[16:33] <ttx> 31% -- Good progress, not impacted by Beta1Freeze or release process
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-papercuts
[16:33] <ttx> 33% -- On track (one WI per week). 43% of the target bugs fixed so far
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-eucalyptus-merging-and-packaging
[16:33] <ttx> 33% -- On track (one WI per week)
[16:34] <ttx> Bugs affecting server, in other teams:
[16:34] <ttx> https://bugs.launchpad.net/bugs/506297
[16:34] <ttx> slangasek: are we still on track to fix that one ?
[16:34] <ttx> our servers look damn good though, now
[16:34] <slangasek> multi-network setup> is this going to be addressed in time?
[16:35] <slangasek> the plymouth fixes are later than expected, but that particular bug should shake out along with all the rest of the refactoring
[16:35] <ttx> slangasek: I hope so. The fallback plan is to use the local test rigs to do that testing
[16:35] <ttx> if we can't automate it
[16:35] <Keybuk> slangasek: I'm in a good progress with that one
[16:35] <slangasek> so there's no point in poking at it individually as long as Keybuk is still reworking plymouth's VT handling at large
[16:35] <Keybuk> will probably hack over the weekend on it
[16:36] <Keybuk> but it's good
[16:36] <ttx> https://bugs.launchpad.net/bugs/524439
[16:36] <slangasek> Keybuk: how soon do you think it will land?
[16:36] <ttx> I think cjwatson is on it
[16:36] <Keybuk> slangasek: by monday
[16:36] <slangasek> Keybuk: excellent
[16:36] <cjwatson> 524439> I have been doing little else for the last three days
[16:36] <Keybuk> it's obviously just slow to test
[16:37] <ttx> https://bugs.launchpad.net/bugs/527208 (kernel)
[16:37] <cjwatson> again, just slow to test
[16:37] <slangasek> Keybuk: is there a branch it's worth having me help test / look at yet?
[16:37] <ttx> jjohansen was hoping for a fix before EOW
[16:37] <ttx> jjohansen1: any updated status ?
[16:37] <Keybuk> slangasek: only in GIT, and I'd have to push that upstream - and it's not cleaned up yet
[16:38] <slangasek> ok
[16:38] <Keybuk> so I'd rather not, since fdo's git server only likes fast-forward pushes and stuff
[16:38]  * slangasek nods
[16:38] <slangasek> anything else on server?
[16:38] <jjohansen1> ttx:  sorry haven't tracked it down yet, working on it
[16:38] <ttx> jjohansen1: ok, thanks
[16:38] <ttx> slangasek: no.
[16:39] <slangasek> [TOPIC] Mobile Team
[16:39] <MootBot> New Topic:  Mobile Team
[16:39] <slangasek> ttx: thanks
[16:39] <slangasek> asac: hit me
[16:39]  * ogra looks up
[16:39] <asac> hard?
[16:39] <asac> :)
[16:39] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:39] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:39] <asac> so I came back on Thu, so i started the rebuild for thumb2 yesterday
[16:40] <asac> did that in a native ppa, but outcome was surprisngly good
[16:40] <ogra> nearly 1/§ done \o/
[16:40] <ogra> *1/3
[16:40] <asac> we have 86/323 (not 100% accurate)
[16:40] <ogra> nearly ...
[16:40] <ogra> rounded ...
[16:40] <slangasek> asac: hum, why in a PPA?
[16:40] <asac> packages now build there ... will get them pocket copy and proceed in similar chunks in the archive on weekend
[16:40] <ogra> ;)
[16:40] <asac> slangasek: because i dditn want to risk loads of packages coming back as ftbfs, keeping us out of sync etc.
[16:41] <asac> the ppa build worked well, so i will continue in archive
[16:41] <slangasek> ok; further chunks will be in the archive so we don't have the pocket copy overhead, great
[16:41] <slangasek> (human overhead)
[16:41] <asac> https://edge.launchpad.net/~asac/+archive/armel1/+packages
[16:41] <ogra> was just to minimize the risk
[16:41] <asac> slangasek: found that cdrkit and cdrdao ftbfs on all archs
[16:41] <slangasek> is 326 the total count of packages needing rebuild?
[16:41] <asac> so some  postitivefall out
[16:41] <asac> slangasek: yes, round about ... i think its 323
[16:41] <asac> but far less than i initially thought
[16:42] <asac> and 80 packages built within less a day on all archs ... so seems like we will get most done this weeken
[16:42] <asac> d
[16:42] <slangasek> excellent
[16:42] <asac> assuming builders will be idle with everyone else doing weekend ;)
[16:42] <ogra> well, plus possible ftbfs overhead
[16:42] <asac> so i will file the bugs on the few packages that failed everywhere
[16:43] <ogra> which will need manual intervention indeed
[16:43] <asac> we only have one or two armel specific failures there atm
[16:43] <slangasek> I see you're waiting on FFes; I'll make sure to look at those today
[16:43] <asac> thanks
[16:43] <asac> so the other big thing is openoffice "uno" investigation
[16:43] <asac> michael is working full time on that
[16:44] <asac> with ARM toolchain guys
[16:44] <asac> he is probably going for a as-long-as-required sprint really soon to UK to get that nailed down
[16:44] <asac> bug 417009
[16:45] <asac> the other issue we are investigating is qemu breakage
[16:45] <ogra> i suspect i found a workaround though
[16:45] <asac> it seems like IO goes bad after installing loads of packages (didnt see that with small package set before)
[16:45] <ogra> testing is still ongoing
[16:45] <asac> its bug 532733
[16:46] <asac> as ogra said, he might have found a workaround ... but we have to keep an eye on this
[16:46] <ogra> right
[16:46]  * slangasek nods
[16:46] <asac> ok Image Status:
[16:46] <asac> imx51 and dove in good shape
[16:46] <asac> thats good news at least ;)
[16:46] <slangasek> the rest of https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid looks self-explanatory to me; any trouble spots we should discuss?
[16:46] <asac> let me check
[16:47] <ogra> likewise ?
[16:47] <asac> bug 517300 might be something serbver team wants to keep on radar
[16:47] <asac> ack
[16:48] <asac> and bug 512959 scares me a bit because it shows that there are still bunch of issues potentially hidden in the toolchain - lets hope that doesnt cause issues elsewhere
[16:48] <slangasek> hmm, ttx is gone
[16:48] <asac> michael has submitted a patch afaict
[16:48] <slangasek> [ACTION] slangasek to follow up on bug #517300 with NCommander
[16:48] <MootBot> ACTION received:  slangasek to follow up on bug #517300 with NCommander
[16:49] <ogra> slangasek, err, with the server team rather ?
[16:49] <slangasek> right, a patch that he acknowledges is untested; I'll try to get him directed to our internal AD test setup
[16:49] <asac> slangasek: remember that NCommander cannot really spend much time on that because he has to do the openoffice stuff
[16:49] <slangasek> ogra: the server team doesn't have ARM hardware
[16:49] <asac> so dont confuse his priorities ;)
[16:49] <slangasek> the last comment says he would support the client side; do you want that part assigned to someone else?
[16:49] <ogra> slangasek, the mobile team will happily help them but i think it makes sense if they drive it as the package owner
[16:50] <ogra> slangasek, for submitting the patch upstream apparently things like copyright assignment are required etc ...
[16:50] <asac> slangasek: i think he says he will help to test
[16:50] <ogra> that should be rather handled by the team thats familiar with upstream
[16:50] <slangasek> ogra: impractical unless you're giving them root access on ARM hardware somewhere for this
[16:50] <asac> after they integrate the patch he submitted
[16:50] <asac> slangasek: thats doable
[16:50] <asac> if they dont need control over power knobs etc.
[16:50] <ogra> sure
[16:51] <slangasek> asac: also, should this really be a priority given that likewise-open is supported as a server component?  Are you expecting ARM server deployments in lucid?
[16:51] <slangasek> [ACTION] slangasek to follow up on bug #517300 with asac/ogra
[16:51] <MootBot> ACTION received:  slangasek to follow up on bug #517300 with asac/ogra
[16:51] <slangasek> there, action amended :)
[16:51] <asac> slangasek: server is an interesting market
[16:51] <ogra> we build server alternate
[16:51] <asac> slangasek: we see multi core arm things with really low power
[16:51] <ogra> we dont fully support them (yet)
[16:51] <slangasek> anything else on mobile?
[16:51] <asac> not fully supported, but we run the server image
[16:52] <asac> and having that is good.
[16:52] <asac> nope
[16:52] <asac> thanks!
[16:52] <slangasek> [TOPIC] Kernel Team
[16:52] <MootBot> New Topic:  Kernel Team
[16:52] <slangasek> asac, ogra: thanks
[16:52] <ogra> in any case we have a commitment to fix as much of main FTBFS as possible
[16:52] <ogra> thanks
[16:52] <slangasek> apw, ogasawara: hi
[16:52] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Beta-1 activity is summarised at the second URL below, with those item pushed out shown as At Risk.  Our burndown chart is at the third URL:
[16:52] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:52] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:52] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:52] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:52] <apw> Of the pushed out items one has now closed.  We have dropped the lenovo-sl-laptop driver as it is confirmed as not required, this closed kernel-lucid-review-of-ubuntu-delta.  The AppArmor pam update is progressing but slowly.
[16:52] <apw>  
[16:52] <apw> For KMS are about ready to upload the drm 2.6.33 backport, testing is ongoing on the packaging for the transition.  Boot performance is progressing slowly, but out boot component remains on track.  The AppArmour upstreaming progresses, feeding updates into Lucid.  For suspend/resume we hav some new timeing patches applied.  Of the bugs on the list two are pending testing by users, and two remain under investigation.

[16:53] <slangasek> drm 2.6.33 backport - is that being pulled in to the main kernel package?
[16:53] <apw> yes, directly into the kerenl
[16:53] <slangasek> ok
[16:54] <apw> not a backport in the sence of lbm
[16:55] <pitti> apw: I saw the bug today, and it sounded like it'd need another patch from trunk?
[16:55] <pitti> apw: but otherwise, thanks so much for getting it so far!
[16:55] <apw> yeah i need to change that one up and find out what happened with that patch
[16:56] <slangasek> apw: "AppArmor pam update" - namespace collision?
[16:57] <apw> there is an update to pam for apparmor in testing as i understand things
[16:57] <slangasek> why does pam need an update?
[16:57] <apw> jjohansen1, ^^
[16:57] <slangasek> jjohansen1: we can take that offline
[16:57] <apw> i'd have to defer to john on that one
[16:57] <slangasek> we don't need to block the whole release meeting with my attachment to the pam package :)
[16:58] <apw> hehe :)  ok
[16:58] <cjwatson> are you guys tracking foundations-lucid-laptop-mode-tools-integration?
[16:58] <apw> i have it on my chart yes
[16:58] <jdstrand> I don't have all the details, but that should be the pam_apparmor module-- not all of pam
[16:58] <jdstrand> beyond that, I can't speak to it
[16:59] <cjwatson> apw: do you know if the remaining two WIs are likely to get done for beta-1?
[16:59] <slangasek> jdstrand: hum, haven't heard of / seen this module before?
[16:59] <apw> cjwatson, thouse two have been slipping, amit has been otherwise engaged this week
[16:59] <jdstrand> slangasek: it's new
[16:59] <slangasek> ok
[16:59] <apw> i have not heard they won't make beta-1 but i will poke the nest and make sure
[16:59] <jdstrand> well, old, but new to Ubuntu
[16:59] <cjwatson> is it safe to slip them to beta-2, or would it be safer to defer them?
[16:59] <slangasek> apw: thanks (that was going to be my next question)
[16:59] <cjwatson> (I don't really know the details)
[16:59] <apw> they look to be the only ones he has which are beta-1 metarial
[17:00] <slangasek> the WIs are weak-FF material
[17:00] <slangasek> implementing power management stuff we aren't currently doing by default
[17:00] <slangasek> so I don't want that slipping to beta-2
[17:00] <apw> slangasek, ack ...
[17:01] <slangasek> anything else on kernel?
[17:03] <slangasek> [TOPIC] Desktop Team
[17:03] <MootBot> New Topic:  Desktop Team
[17:03] <slangasek> apw: thanks
[17:03] <slangasek> pitti: hi
[17:03] <pitti> Full report with weekly summary, RC bug status, and spec status at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <pitti> executive summary of desktop status:
[17:03] <pitti>  - A few WIs moved from Alpha-3, but A3 was by and large a nice precision landing
[17:03] <pitti>  - Beta-1 has a lot of WIs at first sight, but much of it is DX integration, and a good chunk are targets of opportunity
[17:03] <pitti>  - Most pressing items right now:
[17:03] <pitti>    * Fix DRM for ATI/nouveau by DRM kernel backport (bug 507148)
[17:03] <pitti>    * Finish F-Spot image editing for non-imported images
[17:03] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <pitti> ^ (that was just discussed sufficiently)
[17:03] <pitti> called out specs:
[17:03] <pitti>  - desktop-lucid-default-apps: Remaining important TODO is to get image editing into F-Spot without importing pictures (GIMP removal); Chris Halse Rogers is on it, making good progress. But this will land late and require a FFE.
[17:03] <pitti>  - desktop-lucid-startup-speed: from the desktop side we call this pretty much finished, as in "that's as far as we can get". Didier still has a pending ubiquity merge proposal for background caching, and OLS team needs to defer sync daemon startup
[17:04] <pitti> - desktop-lucid-new-firefox-support-model: Remaining one for Beta-1 is to identify extensions to be kept in archive; Chris Coulson has started in the team now and picking up this work
[17:04] <slangasek> pitti: f-spot> how late?
[17:04] <pitti> next week, I hope
[17:04] <pitti> beta-1, in either case
[17:04] <slangasek> ok
[17:04] <pitti> it's a relatively isolated feature, so it can be tested thoroughly
[17:05] <cjwatson> pitti: pending merge proposal> no he doesn't ... ;-)
[17:05] <pitti> cjwatson: rockin'!
[17:05] <pitti> that's what I get for preparing my notes before the meeting :-P
[17:05] <slangasek> heh
[17:05] <Riddell> Kubuntu?
[17:05] <pitti> slangasek: the fallback, if that turns out to be infeasible might be to put back gimp
[17:06] <pitti> slangasek: but I talked to RAOF yesterday (who joined the team now), and he's positive that it should be doable
[17:06] <pitti> Riddell: I'm done, please go ahead
[17:06] <Riddell> #
[17:06] <Riddell> KDE integration patches for Firefox merged in, waiting on upload and on MIR 531848
[17:06] <Riddell> # kdebindings now built on ARM (a workaround not a fix but good enough for now), with any luck we'll get images this afternoon
[17:06] <Riddell> # New logo still being worked on by Canonical Design Team, this'll break art freeze in a couple of places
[17:06] <Riddell> # Upgrade testing/fixing is the priority for next week
[17:06] <Riddell> #
[17:06] <Riddell> https://wiki.ubuntu.com/Kubuntu/Todo
[17:06] <slangasek> pitti: putting back gimp> surely we haven't left room on the desktop ISO for that...
[17:06] <Riddell> # Fixed milestoned bugs this week *  526488 plasmoids overlap on startup
[17:07] <ScottK> Bug #531697 has All Qt/KDE apps blocked on IA64.  It would be good to get someone to look at it.
[17:07] <Riddell> # 9 milestoned bugs marked as kubuntu http://tinyurl.com/yjybcx9
[17:07] <pitti> slangasek: yes, it'd be 6 MB; but I don't think we have to
[17:07] <ScottK> (sorry Riddell, thought you were done)
[17:07] <pitti> uh, you actually care about ia64?
[17:07] <Riddell> am now :)
[17:08] <cjwatson> problems in basic libraries on ports do tend to produce a hell of a lot of build failure mails, at least
[17:09] <ScottK> pitti: We've managed to build on all the ports archs for the last two releases.  It'd be a shame not to for the LTS.
[17:09] <slangasek> Riddell: have the design team given an ETA for this new logo?
[17:10] <Riddell> slangasek: hard to pin down these creative types, but they promised more on Monday
[17:10] <slangasek> hmm
[17:11] <Riddell> it's mainly an issue for the plymouth splash which needs to be implemented on the technical side too, but tseliot says it's not hard
[17:11] <slangasek> Riddell: when they do give you more, can you ask them for an ETA on when they'll be finished with it all? :)
[17:11] <cjwatson> Riddell: also gfxboot splash
[17:11] <cjwatson> I imagine
[17:11] <Riddell> cjwatson: yes, good point
[17:12] <Riddell> slangasek: I'll crack my whip at them
[17:13] <slangasek> thanks :)
[17:13] <ScottK> cjwatson: If we don't get the ICE for IA64 fixed we'll want to go back and consider qt4-x11 binaries and all the rdepends on IA64 for removal under the unbuildable binaries spec.
[17:14] <slangasek> ScottK: I didn't think we were doing per-arch removals?  That risks reintroducing bootstrapping headaches
[17:15] <ScottK> Depends on how far down you go.
[17:15] <ScottK> We'd consdered it just for Universe anyone on the theory Main would get fixed to build.
[17:15] <ScottK> anyone/anyway
[17:16] <slangasek> we can discuss that further offline if you think there's a need
[17:16] <slangasek> (I need to make some headway on unsupportable binaries this week, to start with...)
[17:16] <slangasek> anything else on desktop?
[17:17] <ScottK> OK
[17:18] <slangasek> [TOPIC] DX Team
[17:18] <MootBot> New Topic:  DX Team
[17:18] <slangasek> pitti, Riddell, ScottK: thanks
[17:18] <slangasek> davidbarth: hi
[17:18] <davidbarth> slangasek: hi
[17:18] <davidbarth> report at the usual place: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:18] <davidbarth> summary for this week
[17:19] <davidbarth> gtk csd got deferred to L+1; judged too risky at this stage for an LTS
[17:19] <davidbarth> cody and seb128 did an awesome job of fixing tons of issues, but it's an lts, so...
[17:19] <slangasek> what's been deferred, precisely?  I thought the csd patches already landed
[17:19] <slangasek> is it being reverted?
[17:19] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:19] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:19] <pitti> yes, they got reverted
[17:20] <davidbarth> slangasek: it is reverted, yes
[17:20] <slangasek> ok
[17:20] <davidbarth> seb128 reverted the patch set
[17:20] <davidbarth> the new theme does not depend on them, so the impact should be nil
[17:21] <davidbarth> reporting on the blueprints targeted for the meeting:
[17:21] <pitti> well, the impact is that the reversion fixes a couple of bugs :)
[17:21] <davidbarth> dx-lucid-application-indicator
[17:21] <davidbarth> 2 app ports remaining: hplip (print jobs) and vino
[17:21] <slangasek> hplip, not cups?
[17:21] <pitti> cups itself doesn't have any GUI
[17:21] <pitti> that wuold be system-config-printer
[17:21] <slangasek> well, system-config-printer ties to cups, not to hplip :)
[17:21] <pitti> hplip has its own Qtish icon
[17:22] <slangasek> ok
[17:22] <davidbarth> slangasek: tracking the print job manager that does put an icon on the panel
[17:22] <davidbarth> pitti: right
[17:22] <slangasek> (yes, it does, but it's not installed by default and I never use it despite the HPness of my printer setup :)
[17:22] <davidbarth> nice to have, UI change is limited; target of opportunity has pitti said
[17:22] <davidbarth> the next one is more annoying:
[17:22] <davidbarth> dx-lucid-me-menu
[17:23] <davidbarth> missing dialog to set a custom status; implies 2 new strings and UI (screenshot / doc) change
[17:23] <pitti> davidbarth: TBH, I wouldn't waste time on it
[17:23] <davidbarth> missing about-me simplification; similar issues
[17:23] <davidbarth> pitti: yeah, but as it's listed, so i do report
[17:23] <pitti> davidbarth: wrt. me-menu, is it planned to not show the microblog input field if gwibber isn't running/you don't have twitter accounts defined?
[17:23] <davidbarth> these 2 are also nice to have items; the menu works without them, but be better
[17:24] <davidbarth> pitti: yes, that's a bug; ken indicated the api i could call to fix that
[17:25] <slangasek> davidbarth: actually, the way the application-indicator whiteboard is set up, those app porting items aren't picked up as work items at all; if you mean them to be, you need to not have a blank line before them
[17:25] <davidbarth> so on the me menu, i'll submit a finished patch next week for about-me and will fill the paperwork
[17:25] <davidbarth> slangasek: oh
[17:26] <davidbarth> slangasek: well, at least now most are DONE
[17:26]  * slangasek nods
[17:26] <davidbarth> the rest is for information on other BP:
[17:26] <davidbarth> dx-lucid-messaging-indicator
[17:26] <davidbarth> the beta-1 release completes the work on the new command items feature, with both static (.desktop based) and dynamic actions
[17:26] <davidbarth> all string changes landed
[17:26] <davidbarth> some minor UI tweaks required (arrow in menus to highlight currently running applications)
[17:27] <davidbarth> dx-lucid-indicator-sound
[17:27] <davidbarth> "output on mute" warning still being worked on; should be available next week
[17:27] <davidbarth> dx-lucid-session-menu
[17:27] <davidbarth> String changes landed (shut down -> power off) along with a set of patches for other modules that were using the same wording
[17:27] <davidbarth> dx-lucid-notifications
[17:27] <davidbarth> working on a patch for nm-applet to avoid spurious notifications when reconnecting (UbuntuBug:460144)
[17:27] <davidbarth> err, the formating is not great; it's mostly in the report
[17:28] <slangasek> is "power off" the new wording?
[17:28] <davidbarth> slangasek: indeed
[17:28] <slangasek> (gnome-session changelog said "switch off"; I haven't restarted my session since then, but if it was "switch off" I was going to have to file a buG :)
[17:28] <davidbarth> ted tracked down occurences of that in other packages
[17:28] <slangasek> because "switch off" is jarringly unfamiliar in en_US
[17:29] <slangasek> but "power off" is just fine, so no problem!
[17:29] <davidbarth> slangasek: hmm, i wouldn't be the best to comment on that ;)
[17:29] <slangasek> anything else on DX?
[17:29] <davidbarth> questions on the other blueprints?
[17:29] <slangasek> none from me
[17:29] <slangasek> [TOPIC] Foundations Team
[17:30] <MootBot> New Topic:  Foundations Team
[17:30] <slangasek> davidbarth: thanks
[17:30] <slangasek> cjwatson: 30 seconds ;)
[17:30] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:30] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:30] <cjwatson> as the server team would put it, "updated a couple minutes ago for freshness" - i.e. written in a rush during the meeting
[17:30] <cjwatson> bug centres continue to be plymouth and ubiquity/kubuntu, both in hand but there are a fair few bugs related to each
[17:30] <cjwatson> gfxboot splash for new brand delivered by design team for Ubuntu, pending integration (but I believe documenters are aware of the UI freeze break)
[17:30] <cjwatson> remaining spec work is principally tidy-ups, aside from:
[17:30] <cjwatson>  * language pack removal in oem-config
[17:30] <cjwatson>  * hints file for support-timeframe-information
[17:30] <cjwatson>  * Java and X confirmation for release-collaboration-with-debian
[17:31] <cjwatson>  * most of supportable-binaries
[17:31] <cjwatson>  * kernel work in laptop-mode-tools-integration
[17:31] <cjwatson> the first of those is in hand, I gather the fourth is as well, the third I think is in sync even if not all the is are dotted and ts crossed, the second and fifth I'm unsure about
[17:31] <cjwatson> but the second isn't (I think) b1-critical
[17:32] <slangasek> third is in sync, but I haven't confirmed that there's a committment (even soft) to stay that way for release, which is what I want to sort before checking the box
[17:32] <cjwatson> indeed
[17:33] <slangasek> I think I'm pretty clear on the status here, otherwise; anyone else have questions?
[17:34] <slangasek> [TOPIC] Security Team
[17:34] <MootBot> New Topic:  Security Team
[17:34] <slangasek> cjwatson: thanks
[17:34] <slangasek> jdstrand: go go go!
[17:34] <jdstrand> o/
[17:34] <jdstrand> I may be able to make the 30 seconds
[17:34] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <jdstrand> you can also see from http://people.canonical.com/~pitti/workitems/canonical-security.html that we are on track
[17:35] <jdstrand> we are committed to the essential items from the first link. of those, the only item that is left is security-lucid-libvirt-apparmor-devel, which is mine and doesn't require a FFe. I hope to get to that within the next week or two.
[17:35] <jdstrand> in terms of devel work, we are mostly in bug fixing mode
[17:36] <jdstrand> (that's it from me)
[17:36] <slangasek> great, thanks
[17:36] <slangasek> any questions for security?
[17:36] <slangasek> [LINK] MOTU
[17:36] <MootBot> LINK received:  MOTU
[17:36] <slangasek> jdstrand: thanks
[17:37] <jdstrand> sure! :)
[17:37] <slangasek> ScottK: hi, anything to say here?
[17:37] <ScottK> Looks like that's just me today
[17:37] <ScottK> ocaml transition in ongoing (waiting on the next round of syncs)
[17:37] <ScottK> Python still has me nervous.
[17:37] <ScottK> Nothing else.
[17:37] <ScottK> Any questions?
[17:38] <slangasek> don't think so
[17:38] <slangasek> python nervousness>  we still have an action to review that status next week, so
[17:39] <pitti> ScottK: I saw a ping to bug 530305 an hour ago, is there more to it?
[17:39]  * pitti will work on that now
[17:39] <ScottK> pitti: That's the current action that I know of.  Thanks.
[17:41] <slangasek> [TOPIC] AOB
[17:41] <MootBot> New Topic:  AOB
[17:41] <slangasek> anything else?
[17:41] <slangasek> #endmeeting
[17:41] <MootBot> Meeting finished at 11:41.
[17:41] <slangasek> thanks, all!
[17:41] <pitti> thanks everyone, and enjoy the weekend