[15:59]  * skaet waves
[15:59]  * joshuahoover waves
[16:00]  * rsalveti waves
[16:00] <skaet> hi all,  just about time to get started.
[16:00]  * rsalveti will cover ogra again today
[16:00] <skaet> thanks rsalveti.  :)
[16:00] <skaet> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is skaet.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <skaet> Reminder:   please use ".." on separate line when you've finished typing.    If someone wants to comment on the last point, please "o/", so we know to wait.
[16:01] <skaet> [Topic] Natty overview - skaet
[16:01] <skaet> Agenda is at: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-01-07
[16:01] <skaet> Alpha 2 tasks, as indicated by the burn down charts are starting indicate progress again after holiday break, but overall above trend line.  see: http://people.canonical.com/~platform/workitems/natty/all-natty-alpha-2.html
[16:01] <skaet> Milestoned bugs for alpha2 can be found https://bugs.launchpad.net/ubuntu/+bugs?field.milestone=33572.   We've got a couple critical it would be nice to get closed soon.
[16:01] <MootBot> New Topic:  Natty overview - skaet
[16:02] <skaet> ..
[16:02] <pitti> o/
[16:02] <ScottK> \o
[16:02] <zul> hi
[16:02] <Daviey> o/
[16:03] <skaet> hi pitti, ScottK, Daviey questions? or just saying hi  :)
[16:03] <pitti> skaet: just waving hello
[16:03] <pitti> forgot that it's now an official symbol :)
[16:03] <skaet> :)
[16:03] <ScottK> skaet: waving hello.
[16:03]  * ScottK didn't know it was.
[16:03] <Daviey> skaet, Just saying hi - sorry :)
[16:04] <skaet> ScottK, Daviey, no worries - glad you said hi.  :)
[16:04] <skaet> I'll move on to the other stuff..
[16:04] <skaet> [Topic] update on action items - skaet
[16:04] <skaet> Linaro Natty Freeze milestones have been indicated on https://wiki.ubuntu.com/NattyReleaseInterlock
[16:04] <skaet> There is a tutorial on linker order under development and available for review/comment.  https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition
[16:04] <MootBot> New Topic:  update on action items - skaet
[16:04] <skaet> ..
[16:05] <skaet> any questions?  or further updates to the action items?
[16:05] <ScottK> skaet: What progress on the DSO linking documentation?
[16:05] <ScottK> Ah.
[16:05] <ScottK> I should read all the way down
[16:05] <skaet> ScottK,  :)
[16:06] <skaet> Allison and Matthias welcome comments to the wiki.    Still incorporating some feedback, but hope to broadcast it to the devel list soon.
[16:06] <skaet> ok, not seeing other questions, so on to the round tables..
[16:07] <skaet> [Topic] QA team update - marjo
[16:07] <MootBot> New Topic:  QA team update - marjo
[16:07] <marjo> hi folks; happy new year!
[16:07] <marjo>  * Natty 11.04 Release goals
[16:07] <marjo>  http://people.canonical.com/~pitti/workitems/natty/canonical-platform-qa-natty-alpha-2.html
[16:07] <marjo>  Good progress but blocked on 1 work item.
[16:07] <marjo>   * Bugsquad Roadmap: 'Add support information to bug reporting guidelines' blocked due to http://launchpad.net/bugs/692787 bdmurray following up with Launchpad team.
[16:07] <pitti> marjo: s/~pitti/~platform/ please
[16:07] <marjo> pitti: sorry about that
[16:08] <pitti> marjo: don't be, just to cleanup for the future :)
[16:08] <marjo> pitti: you're too kind; thx
[16:08] <marjo>  * ISO Smoke Test project - Good progress. Should be available for daily use before Alpha-2.
[16:09] <pitti> o/
[16:09] <marjo> # weekly testing status:
[16:09] <marjo> http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:09] <marjo>  * Desktop Automated Testing result
[16:09] <marjo>  http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
[16:09] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:09] <marjo> jibel is investigating why some tests did not run today
[16:10] <marjo>  * Server Automated Testing result
[16:10] <marjo>  http://204.236.234.12/view/ISO-server-Natty/?
[16:10] <marjo> ..
[16:10] <skaet> thanks marjo.   pitti?
[16:10] <pitti> marjo: "iso smoke test" sounds interesting; does that do a fully automated install?
[16:11] <jibel> o/
[16:11] <pitti> like, with faking the ubiquity clicks?
[16:11] <jibel> pitti, yes it does.
[16:11] <pitti> awesome
[16:11] <jibel> it downloads the latest iso
[16:11] <jibel> boots it, and run ubiquity by simulating clicks
[16:12] <pitti> jibel: you replaced ara with a python script!
[16:12] <jibel> when the test is finished it uploads the results to a couchdb which are then published to a hudson serter
[16:12] <jibel> s/serter/server
[16:12] <pitti> (just kidding)
[16:12] <cjwatson> so how do I find out why a given test in http://204.236.234.12/view/ISO-server-Natty/ failed?
[16:12] <jibel> pitti, not all ara
[16:12] <pitti> jibel: just kidding; nice work
[16:13] <cjwatson> like http://204.236.234.12/view/ISO-server-Natty/job/natty-server-amd64_print-server/lastFailedBuild/ say
[16:13] <jibel> hggdh, ^^
[16:13] <marjo> cjwatson: hggdh runs those tests, so he would do the root cause analysis
[16:14] <cjwatson> so it's dependent on an operator to analyse them?
[16:14] <cjwatson> I was hoping I could just download the d-i syslog from a failed run
[16:14] <hggdh> cjwatson: yes, it depends on review for the cause of failure
[16:14] <marjo> cjwatson: in some sense, yes
[16:15] <cjwatson> obviously it has to be reviewed but I was hoping that a competent developer might be able to do that review too
[16:15] <hggdh> cjwatson: we do not currently save the d-i log (i.e., /var/log/installer). This can be done, though
[16:15] <cjwatson> what I'm asking is what information you're using when you do that review
[16:15] <marjo> cjwatson: sometimes, one can look at the console output and do some quick analysis
[16:15] <cjwatson> if you don't have the d-i syslog I'm having trouble seeing how you would get any useful results at all
[16:17] <hggdh> cjwatson: to zero in the last failure, lick on the run # to the right of the "Last failure". Then you can look at the Console output and the build artifacts links
[16:17] <marjo> cjwatson: thx for the suggestion; will investigate for inclusion
[16:17] <cjwatson> I can't find any actual useful information in the build artifacts; that's why I asked :-)
[16:17]  * skaet looks around to see if there are other questions?
[16:18] <marjo> hggdh: then one of the build artifacts can be the d-i log?
[16:18] <marjo> skaet: we'll continue discussion w/ cjwatson & hggdh off-line
[16:18] <skaet> thanks marjo, hggdh, jibel.  :)
[16:19] <skaet> [Topic] Hardware Certification team update - victorp
[16:19] <MootBot> New Topic:  Hardware Certification team update - victorp
[16:19] <victorp> weekly testing this week run for clients
[16:19] <victorp> [LINK] http://people.canonical.com/~hwcert/hw-testing/current
[16:19] <MootBot> LINK received:  http://people.canonical.com/~hwcert/hw-testing/current
[16:20] <victorp> Servers - we have both lab and image issues discuss previously
[16:20] <victorp> we are planning to start looking at the untested systems to bring up coverage
[16:20] <victorp> and also to keep up weekly testing ongoing from now on
[16:21] <victorp> we had 2 new starters in the team this week, so I am confident that it will help
[16:21] <skaet> :)
[16:21] <victorp> we are trying to organise cover for next week as everyone in the lab is travelling to dallas
[16:21] <victorp> we need someone to press the reboot button ;)
[16:22] <victorp> back in montreal  - but we should be able to manage
[16:22] <victorp> that is all from me
[16:23] <skaet> thanks victorp.
[16:23] <skaet> will we start to see boot performance tests again after the rally?
[16:23] <victorp> that is the plan yes :)
[16:23] <skaet> excellent.  :)
[16:24] <skaet> any other questions?
[16:24] <victorp> note that the data is collected on the same test - we need to understand how we report the results
[16:24] <skaet> not doing it the same way ameet did before/
[16:25] <skaet> ?
[16:25] <cjwatson> just bootchart png and tar, I'd have expected?
[16:25] <cjwatson> or svg and tar, whatever it is
[16:25]  * victorp hwcert team running a head of time -> http://people.canonical.com/~cr3/desktop/public_html/daily-bootcharts/
[16:26] <victorp> ^^ first set of results for bootchart on 2011 available
[16:26] <cjwatson> those are reporting the desktop starting up in negative time
[16:26] <skaet> victorp,  not seeing any 2011 dates on the last tested column?
[16:26] <cjwatson> I know the desktop team are good but they aren't that good :)
[16:27] <victorp> do a refresh? first one on the list
[16:27] <skaet> victorp,  yup, seeing it now.   thanks!
[16:28]  * skaet does happy dance - new data to study...
[16:28] <victorp> cjwatson - I believe that is the difference from previous dance
[16:28] <victorp> s/dance/run/
[16:28] <victorp> skaets fault!
[16:28] <victorp> :)
[16:28] <skaet> lol
[16:28] <skaet> any other question?
[16:28] <pitti> do we have any SSD systems there?
[16:28] <cjwatson> victorp: are you sure?  that looks odd based on previous data, and in any case we need absolute numbers too
[16:29] <pitti> ah, mini 10 v
[16:29] <victorp> oh yes, I see what you mean when you drill down on the data
[16:29] <cjwatson> plus, the kernel time given there is very close to the time it takes the kernel to start up in the bootchart
[16:29] <seb128> do you wait on gnome-panel loading?
[16:29] <pitti> but the last mini 10 report is from last June
[16:29] <seb128> because there is no gnome-panel in unity
[16:30] <victorp> ok - we are not there yet, we are getting started warming up the test machine
[16:30] <seb128> which probably screw the measure for the desktop bit
[16:30] <victorp> :)
[16:31] <skaet> thanks victorp.   nice to see the preview.   not seeing any questions so will move on.
[16:31] <skaet> [Topic] Security team update - jdstrand
[16:31] <MootBot> New Topic:  Security team update - jdstrand
[16:32] <jdstrand> hi
[16:32] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:32] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:32] <jdstrand> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:32] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:32] <jdstrand> Not a lot to report again as we have again been focusing mainly on non-natty duties this week. We/pitti did fix bug #690040 and a related one with ifupdown. We have no pending features for alpha-2.
[16:32] <jdstrand> ..
[16:33] <skaet> Thanks jdstrand!
[16:33] <jdstrand> sure :)
[16:33] <skaet> any one have questions?
[16:33] <skaet> [Topic] Kernel team update - apw
[16:33] <MootBot> New Topic:  Kernel team update - apw
[16:33] <apw> o/
[16:33] <apw> Overall status is reported at the first link below.  Burn down for the release milestone is at the second link below.  Burndown for the cycle is at the third link:
[16:34] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:34] <apw> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-2.html
[16:34] <apw> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:34] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:34] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-2.html
[16:34] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:34] <apw> We are progressing on our natty-alpha-2 items, some of the natty-alpha-1 items remain but we are closing them.  The remaining pushed out items are listed with background on the overall status above (first link).  Overall burndown we are still below the line, so we should be able to catch up.
[16:34] <apw> Of the bugs called out on the agenda: #630748 waits on an Intel microcode update; #542660 waits on feedback from the reporter; #600453 there is upstream progress which is enouraging; #636091 seems to only affect live environments; #681877 is likely related to #600453; #682617 waits on feedback from the reporter, but does not appear to be kernel.
[16:34] <apw> The main distro kernel is now rebased forward to mainline v2.6.37 final and published in advance of the Rally.  This kernel brings back the ARM OMAP3 kernels needed for the ARM images.  Final confirmation of the Kernel version should be made at Rally next week.  There will be an update hiatus during the v2.6.38 merge window, we will likely not upload kernels until -rc2 dependant on stability there.
[16:34] <apw> ..
[16:34] <cjwatson> o/
[16:34] <skaet> go cjwatson
[16:34] <cjwatson> I'd like to meet kernel folks next week to sync up on the state of play on graphics/gfxpayload=linux/etc.
[16:34] <cjwatson> would that be possible?
[16:35] <apw> cjwatson, yes please that would be advisable
[16:35] <cjwatson> there's an entry on the foundations agenda for the rally, so whenever you like really
[16:35] <pitti> o/
[16:35] <cjwatson> ok
[16:35] <apw> cjwatson, please add it to the kernel agenda so we don't forget
[16:35] <cjwatson> ok
[16:35] <apw> cjwatson, ack
[16:35] <skaet> go pitti
[16:35] <pitti> apw: is https://blueprints.launchpad.net/ubuntu/+spec/hardware-desktop-n-xorg-configuration-the-final-ten-percent (move i915 configs to sysfs) still on the table or should we drop it?
[16:36] <pitti> and writable EDID
[16:36] <apw> pitti, that one i have on my list, but have not gotten to it yet, perhaps next week is a good time.  i hear part may already be done
[16:37] <pitti> apw: nice, thanks
[16:37] <pitti> apw: was mainly interested for the sake of planning, as it's a prerequisite for futher development
[16:37]  * skaet looks around...  anyone else?
[16:37] <apw> pitti, ack, we should meet to discuss next week also
[16:38] <skaet> nice detailed summary apw - thanks!
[16:38] <apw> np
[16:38] <skaet> [Topic] Foundations team update - cjwatson
[16:38] <MootBot> New Topic:  Foundations team update - cjwatson
[16:39] <cjwatson> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html
[16:39] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html
[16:39] <cjwatson> Behind the trend line after the holiday, but not too desperately, and there are a number of obvious things we can defer (e.g. client part of donations through software-center, which still has no design and no server), so I'm not worried yet.
[16:39] <cjwatson> Interesting feature progress since last week:
[16:39] <cjwatson>  * Working on moving installer testing to LDTP, which should be more robust and flexible than Sikuli due to ATK named objects
[16:39] <cjwatson>  * Upstart override feature code-complete, tests in progress
[16:39] <cjwatson>  * software-center ratings-and-reviews "almost ready (but not quite :/)", testing against a real server instance
[16:39] <cjwatson>  * Initial LibreOffice packages, as you may have noticed from the news - though this should really be desktop, right? ;-)
[16:39] <cjwatson>  * GRUB btrfs and squashfs support merged from experimental upstream branches - as of tomorrow it *should* be possible to do a full install on btrfs out of the box, with partman/default_filesystem=btrfs
[16:39] <cjwatson>  * Archive test rebuild in progress (doko)
[16:39] <cjwatson> I merged upstream console-setup the other day, which is causing a bit of disruption (I sort of expected this which is why I'd put it off for so long).  Sorry about that.
[16:39] <cjwatson> ..
[16:40] <skaet> Thanks cjwatson.  :)   any progress on the bugs?
[16:40] <doko> fyi, build results will show up here: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110107-natty.html
[16:40] <pitti> cjwatson: FTR, new LibO maintainer will start Feb 1st
[16:40] <cjwatson> very little I'm afraid, we're going to beat the list down at the rally
[16:40] <cjwatson> pitti: thanks, yeah, Robbie said there'd been progress there
[16:40] <skaet> cjwatson,  fair 'nuf.  :)
[16:41] <skaet> any other questions?
[16:41]  * cjwatson agendas that just to make sure
[16:41] <skaet> :)
[16:41] <skaet> [Topic] Server team update - zul/daviey
[16:41] <MootBot> New Topic:  Server team update - zul/daviey
[16:41] <zul> hi
[16:42] <zul> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:42] <skaet> hi
[16:42] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:42] <zul> Happy new year! People are ramping up again. We are falling behind in our burn down charts, but they need to be updated to reflect the relaity. I expect alot of that work will be done next week. We have several bugs on our radar:
[16:42] <zul>  * bug 697753 - bittorrent recommendation prevents bittorrent demotion
[16:42] <zul>     * Upstream will be looking at this and we will be doing a point release next week.
[16:42] <zul>  * bug 697181 - DoS: Infinite loop processing 2.2250738585072011e-308
[16:42] <zul>  * bug 689944 - Fix some ocf script issues
[16:42] <zul> the trend line is a bit depressing but i expect that to clear up next week at the rally.
[16:42] <zul> ...
[16:43] <skaet> Thanks zul!   Will add those bugs to the ones i'm tracking.
[16:43] <zul> np
[16:43] <skaet> looking forward to the trend line improving after the rally.  :)
[16:44] <skaet> any questions?
[16:44] <skaet> [Topic] Desktop team update - pitti
[16:44] <MootBot> New Topic:  Desktop team update - pitti
[16:44] <pitti> Blueprint implementation:
[16:44] <pitti> - On track for entire cycle (http://people.canonical.com/~platform/workitems/natty/canonical-desktop-team.html)
[16:44] <pitti> - Falling behind on alpha-2, seems we need to drop some targets of opportunities; we'll review that on the sprint (http://people.canonical.com/~platform/workitems/natty/canonical-desktop-team-natty-alpha-2.html)
[16:44] <pitti> General status:
[16:44] <pitti> - Latest GTK 3 introduced a new way of doing themes, which now causes our GTK3 apps (Jockey, language-selector, Apport, more to come) to look ugly, as the current murrine theme can't be ported to the new GTK way. We have two options to sort this out, will discuss next week at the sprint.
[16:44] <pitti> - No major change to report, due to holidays
[16:44] <pitti> CD space savings:
[16:44] <pitti> - CDs had been within size limit for some days now, but oversized again starting from today; we took off Rhythmbox now (since Banshee got added), which will save 1.5 MB, and need a langpack refresh for alpha-2 which will save several MB as well, so we are on target for alpha-2.
[16:45] <pitti> - python2.6 package on CDs got fixed, i. e. it's not installed any more.
[16:45] <pitti> - /usr/lib/python2.{6,7} each need ~ 9.5 MB of CD space, i. e. due to the transition we added 9.5 MB. It would be nice if we could drop support for 2.6 during Natty to reclaim them.
[16:45] <pitti> RC bugs:
[16:45] <pitti> - summary: going well, no worries here (two open issues which are in progress)
[16:45] <pitti> - details on [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:45] <pitti> ..
[16:45] <skaet> thanks pitti,  good to hear that we'll be fitting back on the CD for alpha-2. :)
[16:46] <skaet> any one questions?
[16:46] <skaet> [Topic] Ubuntu One Team - joshuahoover
[16:46] <MootBot> New Topic:  Ubuntu One Team - joshuahoover
[16:47] <joshuahoover> [LINK] https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:47] <joshuahoover> details on where we're at with blueprints and releases are in the link above
[16:47] <MootBot> LINK received:  https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:47] <joshuahoover> good news? udf selection is in the latest ubuntuone-client package...needs a new release to work properly from the gui
[16:47] <joshuahoover> bad news? desktopcouch is not in like we thought it would be before the holidays...we have a couple people working on that now to work out the (various) issues
[16:47] <joshuahoover> we'll have some folks at the platform sprint...errr...rally next week & will be looking to make good progress on some unity integration while we're there
[16:47] <joshuahoover> and that's about it
[16:47] <joshuahoover> ..
[16:48] <skaet> thanks joshuahoover!
[16:48] <pitti> joshuahoover: we took off evo-couchdb as Naty said U1 control panel would install it on demand now/soon (she's got a branch)
[16:48] <pitti> joshuahoover: if that's still unclear, let's discuss next week
[16:48] <joshuahoover> pitti: ah yes, there was discussion about this earlier today actually on #ubuntuone
[16:49] <skaet> any other questions?
[16:49] <skaet> [Topic] Kubuntu Team update - Riddell
[16:49] <MootBot> New Topic:  Kubuntu Team update - Riddell
[16:49] <Riddell> yo
[16:49] <Riddell>  * KDE SC 4.5.95 uploading to natty, building now
[16:49] <Riddell>  * KDE SC 4.5.5 update for maverick being packaged by ninjas, due for release shortly
[16:49] <Riddell>  * KDE SC 4.4.5 in lucid-updates, one regression in the packaging, now fixed, bug 696675
[16:50] <Riddell>  * Todo list getting some green but probably behind where I'd like it to be https://wiki.kubuntu.org/Kubuntu/Todo
[16:50] <Riddell>  * 10 kubuntu-tagged bugs targeted for alpha 2 http://goo.gl/yGhJd
[16:51] <skaet> ..?
[16:51] <Riddell> that's me
[16:51] <skaet> Thanks Riddell!   Will dig in and look at those alpha 2 bugs later.  :)
[16:51] <skaet> any questions?
[16:52] <skaet> [Topic] Desktop Experience Team Update - dbarth_
[16:52] <MootBot> New Topic:  Desktop Experience Team Update - dbarth_
[16:52] <doko> Riddell: there seems to be an unneeded promton
[16:52] <doko> cmake b-d
[16:53] <Riddell> doko: I don't understand, what's unneeded?
[16:53] <doko> Riddell: packages in xmlrpc-c were explicitly splitted for the reason of *not* promoting the whole of xmlrpc-c
[16:55] <doko> Riddell: https://bugs.launchpad.net/ubuntu/+source/xmlrpc-c/+bug/369918
[16:55] <dbarth_> oops
[16:55] <dbarth_> hi all
[16:55] <skaet> hi
[16:56] <Riddell> doko: let me look into it to remind myself, I'll get back to you
[16:56] <dbarth_> the report is up at: https://wiki.ubuntu.com/DesktopExperienceTeam/NattyReleaseStatus
[16:56] <dbarth_> not much new this week
[16:56] <doko> Riddell: ok, the new one is bug #698311
[16:57] <dbarth_> we haven't uploaded a release to natty and mostly sorted bugs and landed a couple of infrastructure changes on trunk
[16:57] <dbarth_> re-stabilizing everything after the break
[16:57] <dbarth_> the daily builds should be up and running now to get us ready for next week
[16:57] <dbarth_> of note:
[16:57] <dbarth_> the workflow to get GL bugs passed over to the x team is now in place
[16:58] <dbarth_> https://bugs.launchpad.net/ubuntu/+source/xorg/+bugs?field.tag=natty is their inbound queue
[16:58] <dbarth_> it should ensure a smoother resolution of issues as the tide of unity bugs rises during the cycle
[16:58] <skaet> :)
[16:59] <dbarth_> compiz also is in need for help
[16:59] <marjo> dbarth: fyi, compiz & unity no longer in top 5; http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:59] <dbarth_> we'll be doing some agressive triaging next week, mostly putting aside everything that is not 0.9/unity related
[16:59] <dbarth_> and bringing some resources over to help smspillaz
[17:00] <dbarth_> and last (not on the report, though a lot happened this week as well): a11y is back on track
[17:00] <skaet> ..?
[17:00] <dbarth_> we've been working with apineiro since late december to get the internal plumbing in tplace
[17:01] <dbarth_> (typing slow today)
[17:01]  * skaet sorry
[17:01] <dbarth_> means that the a11y enablement for launcher & panel should be possible
[17:01] <dbarth_> we're also receiving a lot of help from the desktop team here
[17:02] <dbarth_> foundations part: ted is fighting with the gdbus port and appmenu got some more love this week as well
[17:02] <dbarth_> overall we're all waiting for the rally to get all back to full speed in sight of the alpha-2 milestone
[17:02] <dbarth_> bug status
[17:03] <dbarth_> i've updated some of the old bugs with didrocks that were still on the natty radar
[17:03] <dbarth_> and assigned the ones (like the bitesize one) that were still not miletsoned / allocated
[17:03] <dbarth_> that's it mostly
[17:03] <dbarth_> questions? more bugs?
[17:03] <skaet> lol
[17:04] <skaet> there will always be more bugs...
[17:04] <skaet> thanks dbarth_!
[17:04] <dbarth_> well, yes
[17:04] <dbarth_> thx
[17:04] <skaet> [Topic] ARM team update - rsalveti
[17:05] <MootBot> New Topic:  ARM team update - rsalveti
[17:05] <rsalveti> Full Status at https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Natty
[17:05] <rsalveti> ..
[17:05] <rsalveti> - Latest working OMAP4 image is still from 20101214, latest were broken because of the uboot-mkimage removal
[17:05] <rsalveti> - New u-boot package was finally pushed to main, and we'll start getting images again soon! (thanks to lool, doko and ogra)
[17:05] <rsalveti> - Kernel is still 2.6.35 for OMAP 4, TI planning to push a 2.6.38 tree later on
[17:05] <rsalveti> - Kernel for OMAP 3 is back, and we'll soon be able to generate omap 3 images again (thanks to apw)
[17:05] <rsalveti> - Team is back to work, so we should see more work on WI soon
[17:05] <rsalveti> - Most kernel SRU sorted out, just waiting move from proposed to updates
[17:05] <rsalveti> - Firefox is working again with latest package update
[17:05] <rsalveti> ..
[17:05] <rsalveti> Image Status
[17:05] <rsalveti> ..
[17:05] <rsalveti> - Latest working one is from 20101214
[17:05] <rsalveti> ..
[17:05] <rsalveti> Work Items
[17:05] <rsalveti> ..
[17:05] <rsalveti> - Entire http://people.canonical.com/~platform/workitems/natty/canonical-arm.html
[17:05] <rsalveti> - Next Milestone http://people.canonical.com/~platform/workitems/natty/canonical-arm-natty-alpha-2.html - some moved already to alpha 3, and the others to be implemented/discussed during the sprint
[17:05] <rsalveti> ..
[17:05] <rsalveti> Bugs with fix released
[17:05] <rsalveti> ..
[17:05] <rsalveti> - Bug 690445 Firefox crashes on armel
[17:05] <rsalveti> - Bug 673509 Beagleboard-xm chooses a new IP address on each boot
[17:05] <rsalveti> - Bug 653002 omapdss DISPC error: GFX_FIFO_UNDERFLOW, disabling GFX
[17:05] <rsalveti> ..
[17:05] <rsalveti> the whole team is looking forward to work heavily on the WI during the sprint
[17:05] <rsalveti> persia is back on-line, and feeling better!
[17:05] <rsalveti> ..
[17:06] <skaet> glad to hear persia's back online.   :)
[17:06] <rsalveti> yeah :-)
[17:06] <rsalveti> that's all from my side
[17:06] <rsalveti> ..
[17:07] <skaet> thanks for the update rsalveti!    any questions?
[17:07] <skaet> [Topic] MOTU team update - ScottK
[17:07] <MootBot> New Topic:  MOTU team update - ScottK
[17:07] <ScottK> Hello
[17:07] <skaet> :)
[17:08] <ScottK> Not a lot to updates to provide.  People are working on SDO linking, GCC 4.5, and Python2.7 fixes.
[17:08] <ScottK> We won't get to where we really want to be I don't think but progress is being made.  Hopefully Squeeze releases soon and Debian picks up the same toolchain.
[17:09] <ScottK> That's all.
[17:09] <skaet> Thanks ScottK!   figure we'll be seeing linking/gcc/python fixes for a while yet.
[17:09] <skaet> any questions?
[17:10] <ScottK> skaet: Up until the next LTS release is my prediction.
[17:10] <skaet> ack.
[17:10]  * skaet resets her expectations....
[17:10] <skaet> [Topic] Linaro update - JamieBennett
[17:11] <MootBot> New Topic:  Linaro update - JamieBennett
[17:11] <JamieBennett> Hi Kate.
[17:11] <skaet> hi.  :)
[17:11] <JamieBennett> There are not many Ubuntu interlocks from the Linaro sidem we are easier to accommodate this cycle ;)
[17:11] <JamieBennett> Most notable is GCC though.
[17:11] <JamieBennett> We expect a new GCC 4.5 version 2010-02-08 with some basic Android support, heap randomisation and volatile int fixes.
[17:11] <JamieBennett> There will be GDB and improvements but these should be pretty unobtrusive.
[17:11] <JamieBennett> Kernel wise we will probably need another upload early next month (around the same time as the GCC release) but as only Linaro uses this it isn’t a big deal.
[17:11] <JamieBennett> We have initial investigations with Android and MeeGo, I expect some packages to come through REVU into the archive in the coming month or so along with one or two other packages to do with performance, no clear information on that one yet.
[17:12] <JamieBennett> Ubuntu deadline wise we should be fine to get all this in on time
[17:12] <JamieBennett> EOF
[17:12] <skaet> Thanks JamieBennett!
[17:12] <ScottK> JamieBennett: Could there be an action to test build qt4-x11 with the volatile int fixed before it lands?
[17:13] <ScottK> fixed/fixes
[17:13] <JamieBennett> I'm sure its on Michaels radar but give me the action and I'll chase it up
[17:13] <ScottK> skaet: ^^^ Please.
[17:13] <skaet> ack - will do.
[17:14]  * skaet will put it in the minutes.
[17:14] <skaet> any other questions?
[17:15] <skaet> [Topic] any other kudos/comments/questions?
[17:15] <MootBot> New Topic:  any other kudos/comments/questions?
[17:15] <skaet> going once?
[17:16] <skaet> hmm,  looks like end of meeting time
[17:16] <skaet> #endmeeting
[17:16] <MootBot> Meeting finished at 11:16.
[17:17] <marjo> skaet: thx for another effective meeting
[17:17] <skaet> Thanks ScottK, marjo, jibel,  hggdh, victorp, jdstrand, apw, cjwatson, pitti,  zul, daviey, joshuahoover,  dbarth_, rsalveti, JamieBennett
[17:17] <pitti> thanks all
[17:17] <joshuahoover> thank you skaet
[17:17] <pitti> see you all next week!
[17:17] <dbarth_> yep!
[17:17] <skaet> indeed.   looking forward to seeing folks in Dallas!
[17:18] <skaet> and watching the burn down charts improving first hand,  lol.
[17:18] <rsalveti> skaet: thanks!