[16:00]  * victorp waves to skaet
[16:00] <zul> hi
[16:00]  * skaet waves victorp, zul
[16:00] <apw> o/
[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] <Daviey> o/
[16:01] <skaet> hi everyone.  :)
[16:01] <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] <pitti> hello
[16:01] <skaet> Agenda is at: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-02-11
[16:02] <skaet> Milestoned bugs for alpha3 can be found https://bugs.launchpad.net/ubuntu/+bugs?field.milestone=33573.
[16:02] <skaet> [TOPIC] Natty overview
[16:02] <MootBot> New Topic:  Natty overview
[16:03] <skaet> [ACTION] release team needs to revisit release freeze date, and its relation to beta 2.
[16:03] <MootBot> ACTION received:  release team needs to revisit release freeze date, and its relation to beta 2.
[16:04] <skaet> just figured I'd get that one out of the way as something that needs to be looked at.  :)
[16:04] <skaet> reminder that Feature freeze will be coming up on February 24th,  Alpha 3 on March 3rd.
[16:05] <skaet> any other general release issues that need to get high lighted?
[16:05] <skaet> ..
[16:06] <skaet> ok, on to the roundtables..
[16:06] <skaet> [Topic] QA team update - jibel
[16:06] <MootBot> New Topic:  QA team update - jibel
[16:06] <jibel> Hi all!
[16:06] <jibel>  * Natty Alpha 3 Work Items
[16:06] <jibel> http://people.canonical.com/~platform/workitems/natty/canonical-platform-qa-natty-alpha-3.html
[16:06] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-platform-qa-natty-alpha-3.html
[16:06] <jibel> No work items started yet.
[16:06] <jibel> Two additional items were carried over from Alpha-2
[16:06] <jibel> hggdh2 - cloud-server-n-uec-qa - Automate UEC tests setup (image creation, configuration setup)
[16:06] <jibel> hggdh2 - cloud-server-n-uec-qa - Automate user creation on the UEC tests (depends on euca-add-user/other)
[16:07] <jibel>  * QA Dashboard
[16:07] <jibel> http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:07] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/qadashboard/qadashboard.html
[16:07] <jibel> Note linux, libreoffice and unity in both the "Last Day" and "Last 7 Days" metrics
[16:07] <jibel>  * Testing status:
[16:07] <jibel> Desktop Automated Testing results
[16:07] <jibel> http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
[16:07] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/desktop-testing/natty/
[16:07] <jibel> 303 tests in classic desktop and 279 in Unity
[16:08] <jibel> List of bugs found is at the bottom of page.
[16:08] <jibel> Server Automated Testing results
[16:08] <jibel> http://204.236.234.12/view/ISO-server-Natty/?
[16:08] <MootBot> LINK received:  http://204.236.234.12/view/ISO-server-Natty/?
[16:08] <jibel> 3 failures under investigation by hggdh.
[16:08] <jibel> ..
[16:09] <skaet> thanks jibel!   any questions?
[16:09] <skaet> [Topic] Hardware Certification team update - victorp
[16:09] <MootBot> New Topic:  Hardware Certification team update - victorp
[16:09] <victorp> This week we had to skip desktops for the weekly testing, as we were
[16:09] <victorp> shipping them from Montreal to Lexington.
[16:09] <victorp> The report can be found, as usual, at:
[16:09] <victorp> leaks that are causing X to crash:
[16:09] <victorp> [LINK] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/714829
[16:09] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/714829
[16:09] <victorp> We will provide Bryce the information he's asking for.
[16:09] <victorp> On servers we got the best coverage to date :-) All the servers
[16:09] <victorp> scheduled to be certified for 11.04, except one, reported results. We
[16:09] <victorp> are investigating this one, that seems to be an infrastructure issue.
[16:10] <victorp> From the ones that reported back, one failed installation, because of a
[16:10] <victorp> weird memory leak that is causing a failure in grub-installer:
[16:10] <victorp> [LINK] https://bugs.launchpad.net/checkbox-satellite/+bug/716397
[16:10] <MootBot> LINK received:  https://bugs.launchpad.net/checkbox-satellite/+bug/716397
[16:10] <victorp> cjwatson is already on it, and we will provide the information he needs.
[16:10] <victorp> In other areas:
[16:10] <victorp> * we are meeting next week to discuss the future of boot metrics
[16:10] <victorp> * we are suppose to start unity hw compatibility but we haven't got the test suite yet from Unity team.
[16:10] <victorp> ..
[16:10] <cjwatson> o/
[16:10] <cjwatson> er, what?
[16:10] <victorp> ?
[16:10] <cjwatson> I'm not on that bug, seeing as I can't read it
[16:10] <skaet> o/
[16:11] <victorp> oops - that is the link to the checkbox bug
[16:11] <victorp> I will send you the right one
[16:12] <skaet> victorp,  cut/paste error? - not seeing report link.
[16:12] <cjwatson> are you referring to bug 695842?
[16:12] <victorp> yes
[16:12] <cjwatson> there was an out-of-memory there, but it seems to have been transient
[16:12] <victorp> put the wrong bug ;)
[16:13] <victorp> [LINK] http://people.canonical.com/~hwcert/hw-testing/current
[16:13] <MootBot> LINK received:  http://people.canonical.com/~hwcert/hw-testing/current
[16:13] <victorp> ^^ weekly report
[16:13] <cjwatson> the last comment indicates that the grub-installer patch fixed the problem, even though the out-of-memory error was well before grub-installer ran
[16:13] <cjwatson> so I think that can only usefully be chalked up as unreproducible
[16:13] <cjwatson> the fix for 695842 is in -proposed queues and will be ready for testing after 10.04.2
[16:14] <victorp> ok
[16:14] <skaet> thanks for link. :)
[16:14] <victorp> skaet - no probs
[16:15]  * victorp needs to find a better copy/paste way
[16:15]  * skaet looks around, no hands, going on...
[16:15] <skaet> thanks victorp
[16:15] <skaet> [Topic] Security team update - jdstrand
[16:15] <MootBot> New Topic:  Security team update - jdstrand
[16:15] <jdstrand> hi
[16:15] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:15] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty
[16:15] <jdstrand> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:15] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-security.html
[16:16] <jdstrand> For the most part, this last week we have been very busy focusing on stable release updates and have also been fixing security issues in natty. We have no milestoned features or bugs for alpha-3.
[16:16] <jdstrand> In terms of blueprints, I did manage to write and upload aa-disable, which complements aa-enforce and aa-complain for managing apparmor profiles and I wrote some preliminary profiles for telepathy backends. kees has worked on a kernel /proc/net leak patch and has completed updating existing upstart job files with apparmor integration to use the new apparmor-profile-load tool.
[16:16] <jdstrand> We have started tracking a few bugs from other teams that are of particular interest to us. Specifically bug #344878, bug #712662, bug #714908 and bug #714958.
[16:16] <jdstrand> I'm not sure about how to approach these within the context of this meeting, but for now it is fine to simply mention we are watching those.
[16:17] <jdstrand> wrt 714958 we also filed a related bug #715874 which is apparmor profiles for various thumbnailers. All have been started and are available via bzr (and in the bug), but we have not committed to getting those in before feature freeze as it will require a lot of testing and there are other more pressing issues at the moment.
[16:17] <cjwatson> 712662> waiting for doko to return from holiday there
[16:17]  * jdstrand nods
[16:17] <jdstrand> ..
[16:17] <skaet> thanks jdstrand,  appreciate you mentioning the bugs you're watching.
[16:18] <jdstrand> np :)
[16:18]  * skaet looks around for o/'s,  nope not seeing any moving on.  :)
[16:18] <skaet> [Topic] Kernel team update - apw
[16:18] <MootBot> New Topic:  Kernel team update - apw
[16:19] <apw> o/
[16:19] <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:19] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:19] <apw> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-3.html
[16:19] <apw> [LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:19] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty
[16:19] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-3.html
[16:19] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg
[16:19] <apw> The natty-alpha-2 kernel seemed to be holding up pretty well so far.  Since the freeze lifted we have uploaded two kernels with the latest v2.6.38-3.30 (v2.6.38-rc4 based).  These have brought a swathe of fixes for graphics.  Overall we are looking good on longer term tasks with most of the key deliverables complete.  There are few direct deliverabled for natty-alpha-3, we are now tracking mainline and fielding issues as they appear.
[16:19] <apw> Of the bugs called out on the agenda against the kernel, status is as below:
[16:19] <apw> #344878 ecryptfs long filename prototype continues to evolve with a second push going to upstream, we will need to make a decision on disabling this shortly;
[16:19] <apw> #539467 SATA alpm is now disabled in userspace, upstream discussions are ongoing;
[16:19] <apw> #542660, #600453, and #681877 (all black screen issues) are in various stages of testing, results are a mixed bag;
[16:19] <apw> #630748 remains waiting on Intel for updated wireless firmware;
[16:19] <apw> #636091 is looking like a locking issue in USB, possibly to do with the BKL, investigation continues; and
[16:20] <apw> #702090 looks to be an interaction with vesafb, upstream are saying "don't do that".
[16:20] <apw> The other bugs seem to be non-kernel packages, status is recorded on our status page where available (first link above).
[16:20] <apw> ..
[16:20] <skaet> thanks apw!   appreciate the details on the bugs.
[16:21] <cjwatson> o/
[16:21] <skaet> have the the alpha-3 burn tasks been scrubbed?
[16:22] <apw> skaet, everything pushed out of a2 is in a3, but i suspecd thtats not your question
[16:22] <skaet> heh,  nup
[16:23] <skaet> just need to know if the list that's there is complete for summarizing up at this point.
[16:23] <apw> i think so yes
[16:23] <cjwatson> 702090> "don't do that" - is that something plymouth needs to do differently?
[16:23] <skaet> cool thanks!   cjwatson your turn.  :)
[16:24] <apw> cjwatson, not sure as yet.  i think its more fundamental
[16:24] <apw> we would need to hold off injecting vesafb until we know that drm isn't coming
[16:25] <apw> or perhaps stopping plymouth opening it is enough, but definatly
[16:25] <apw> not open /dev/fb0 before it gets swizzled to drm
[16:25] <cjwatson> right, that complicated mess
[16:25] <apw> and thats not a trivial change
[16:25] <cjwatson> hoping to finally dive into some of that this week
[16:26] <apw> cjwatson, then perhaps we can sync up when you do, as i think we are aready waiting for "no more devices" which
[16:26] <apw> might mean we can inject vesafb at that point and avoid this mess
[16:26]  * cjwatson nods
[16:26] <apw> ..
[16:26] <skaet> [Topic] Foundations team update - cjwatson
[16:26] <MootBot> New Topic:  Foundations team update - cjwatson
[16:27] <cjwatson> http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html
[16:27] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html
[16:27] <cjwatson> Still just below the trend line, with half a dozen work items removed this week, but we'll need to accelerate again soon.  We seem to have got pulled into a lot of bug-fixing instead, on the whole.
[16:27] <cjwatson> Interesting progress this week:
[16:27] <cjwatson>  - btrfs installs now confirmed to work properly again, with subvolumes set up so that the upgrade tools will be able to do interesting rollback things.
[16:27] <cjwatson>  - Agreement on Upstart branch maintenance, so the major remaining pieces of work there should start landing soon.
[16:27] <cjwatson>  - Upstart visualisation and interactive boot work.
[16:27] <cjwatson>  - Timezone widget discussions with GNOME; looks like much of Ubiquity's widget will be going upstream.
[16:27] <cjwatson>  - We've been doing some early bootstrapping work on a new ppc64 architecture.  This is still in stage1 bootstrapping but going well so far.
[16:27] <cjwatson> I've been trying to keep the agenda up to date with bug work.  If you care about anything specific, please ask.
[16:27] <cjwatson> ..
[16:28] <skaet> thanks cjwatson,  appreciate you updating the agenda directly.  :)
[16:28] <skaet> are the a3 tasks accurate at this stage for foundations, or do they still need some scrubbing?
[16:29] <cjwatson> as far as work items go, I'm afraid this cycle I've largely only been paying any attention at all to the whole-cycle chart.
[16:29] <cjwatson> I hope that once we have a dedicated manager again, we'll have time to improve this
[16:29]  * skaet nods
[16:29] <skaet> thanks, that answers my question.
[16:30] <cjwatson> on bugs, I think they're OK
[16:31] <skaet> [Topic] Server team update - zul
[16:31] <MootBot> New Topic:  Server team update - zul
[16:31] <zul> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:31] <zul> Hi,
[16:31] <zul> Work items are a bit behind according to the graph, But alot of things are happening behind the scene include working on awstrial, new openstack snapshot, working on LXC on openstack, and new packages including Handbreak plugin for mysql. Eucalyptus still remains to be a problem in Natty.
[16:31] <zul> New Bugs this week:
[16:31] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus/Natty
[16:31] <zul>  * 590201 - qemu-kvm - OpenSolaris (previously working) no longer boots: kernel panics early
[16:31] <zul> ...
[16:31] <skaet> o/
[16:31] <skaet> any update on the bugs called out in the agenda?  is the status there accurate for them?
[16:32] <zul> i think so but ill double check right after the meeting
[16:32] <skaet> thanks.
[16:32] <skaet> also, is the a3 tasks in its burn down accurate?
[16:32] <skaet> s/is/are/
[16:32] <zul> no..i think robbiew still has to go through them
[16:33] <robbiew> tasks are good
[16:33] <skaet> :)
[16:33] <zul> i stand corrected :)
[16:33] <skaet> thanks zul.  any other questions?
[16:33] <robbiew> heh...might do minor swizzles..but that's par for the course
[16:34] <skaet> [Topic] Desktop team update - pitti
[16:34] <MootBot> New Topic:  Desktop team update - pitti
[16:34] <pitti> Blueprint implementation:
[16:34] <pitti> - On track for entire cycle
[16:34] <pitti> - Not much progress on alpha-3 yet; called for updating WI status and dropping 'bonus' ones, but not finished cleanup yet
[16:34] <pitti> - feature development has slowed down a bit, we spent a lot of time doing bug fixing last week
[16:34] <pitti> General status:
[16:34] <pitti> - Most annoying compiz bug about invisible windows should be fixed now
[16:34] <pitti> - python-gobject ABI breakage has been hotfixed, so pygtk apps are running normally again; a better workaround has now landed on the stable pygobject upstream branch
[16:34] <pitti> RC bugs:
[16:34] <pitti> - from this week: 5 fixed, 2 fix committed, 2 new on radar
[16:34] <pitti> - standing out here is bug 637827 which is blocked on Mozilla allowing us to ship the global menu bar extension for Firefox; rest of the bugs are making reasonable progress at this stage
[16:34] <pitti> - details at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus#rcbugs
[16:34] <pitti> ..
[16:35] <skaet> thanks pitti!  :)   when o you think the wi status will be updated?
[16:35] <skaet> s/o/do/
[16:35] <pitti> chasing people; certainly next week
[16:36] <skaet> thanks.  :)
[16:36]  * skaet looking around....
[16:36] <pitti> we currently don't have a team manager either, so I guess the whip cracking is on me
[16:37] <skaet> indeed.  :/
[16:37] <skaet> [Topic] Ubuntu One Team - joshuahoover
[16:37] <MootBot> New Topic:  Ubuntu One Team - joshuahoover
[16:37] <joshuahoover> [LINK] https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:37] <MootBot> LINK received:  https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus
[16:37] <joshuahoover> details on where we're at with blueprints and releases are in the link above
[16:37] <joshuahoover> updates on items at risk:
[16:37] <joshuahoover> 1) u1 shotwell integration is likely not going to happen for natty...we're down a person and the integration with shotwell is going to be harder for us than we originally thought/estimated...i'll have a definitive answer on this by wed. next week
[16:38] <joshuahoover> 2) syncdaemon resumable uploads should be ready on wed., february 16th ...they were blocked for a couple weeks but we've found a way forward and have made good progress
[16:38] <joshuahoover> 3) unity integration has started...we've got the API's we need and are now putting in the progress indicator and testing it all out so we're looking good here
[16:38] <joshuahoover> 4) u1 music store in banshee...we still need to add the ability to tweet about a song and ensure u1 purchases automatically show up like they do in rbox...going to be tight to make it in time for feature freeze...i may be filing freeze exception next week
[16:38] <joshuahoover> overall, with dropping shotwell integration, we're looking pretty good with the exception of the banshee work
[16:38] <joshuahoover> and that's about it
[16:38] <joshuahoover> ..
[16:39] <skaet> thanks joshuahoover!  appreciate the details.
[16:39] <skaet> o/
[16:39] <skaet> is the A3 WI list up to date for your team?
[16:40] <joshuahoover> skaet: yes, should be :)
[16:40] <skaet> thanks!  :)
[16:41]  * skaet has slide making to do today,  hence the questions...
[16:41] <skaet> [Topic] Kubuntu Team update - Riddell
[16:41] <MootBot> New Topic:  Kubuntu Team update - Riddell
[16:41] <Riddell> hi
[16:41] <Riddell>  * Alpha 2 out, plenty of bugs but nothing worrying for this stage in the cycle
[16:41] <Riddell>  * libindicate-qt updated for new API
[16:41] <Riddell>  * Qt now being built with gcc 4.4 to fix issues on ARM
[16:41] <Riddell>  * various space saving changes mean we have some space on the CDs for language packs now (except PowerPC)
[16:41] <Riddell>  * kubuntu mobile mostly working again, seeds split into new collection, some change to launchpad needed to update
[16:41] <Riddell>  * 11 bugs milestoned for alpha 3 http://goo.gl/yGhJd
[16:42] <Riddell> ..
[16:43] <skaet> thanks Riddell!   Is the A3 WI list the one I should look at for the summary,  or Kubuntu to do?
[16:43] <Riddell> https://wiki.kubuntu.org/Kubuntu/Todo is the one we care about, and the milestoned bugs above
[16:44] <skaet> thanks.  will reference that then.  :)
[16:44] <skaet> [Topic] Desktop Experience Team Update - dbarth_
[16:44] <MootBot> New Topic:  Desktop Experience Team Update - dbarth_
[16:44] <dbarth_> hi
[16:44] <dbarth_> weekly status update at: https://wiki.ubuntu.com/DesktopExperienceTeam/NattyReleaseStatus
[16:45] <dbarth_> hightlights for the week
[16:45]  * victorp cjwatson this is the bug in our report https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/715871
[16:45] <dbarth_> for unity shell
[16:45] <dbarth_> All of our key targets were reached
[16:45] <dbarth_> The Dash is in this week, a lot of bug fixes allowed the Shell team to land the full Dash experience; the slow scroll is fixed as well
[16:45] <dbarth_> Progress indicators and counts for the Launcher are there: U1 & FF should soon shine on the new Unity Launcher!
[16:45] <dbarth_> Keyboard navigation for the launcher
[16:45] <dbarth_> The invisible windows bug in compiz is still an issue
[16:45] <dbarth_> however, we've slowed down since the nvidia drivers got broken; it's really hurting the team
[16:46] <dbarth_> foundations got some nice action for this week as well:
[16:46] <dbarth_> Sound menu goes into libunity, consolidating new stable APIs
[16:46] <dbarth_> Calendar integration from EDS
[16:46] <dbarth_> More appmenu stabilization and fixes
[16:46] <dbarth_> Thunderbird support for the global menu is in Natty (after Firefox last week, yeah!)
[16:46] <dbarth_> LibreOffice globalmenu support started this week: aiming for a universe release around natty-beta
[16:46] <dbarth_> More API docs preparation with the Community team
[16:46] <dbarth_> last on the qa front, the Bug Pilot program starting to bear fruits
[16:47] <skaet> ..?
[16:48] <dbarth_> ...
[16:48] <dbarth_> (sorry)_
[16:48] <skaet> thanks dbarth_
[16:48] <skaet> ;)
[16:48] <skaet> o/
[16:48] <cjwatson> victorp: oh, ok, an entirely different one from what I thought then.  Has ara seen my message?  The ball is in her court
[16:48] <victorp> cjwatson, she is off for the day I will ping her on monday
[16:48] <victorp> 0/
[16:48] <victorp> o/
[16:49] <skaet> the link on your NattyStatus refers to the entire burndown, not just the a3.    Are the WI's targetted to A3 accurate?
[16:49] <skaet> dbarth_, ^^
[16:49] <victorp> I had a question in my update before about when will be unity test scripts ready so hw cert can test compatibility. dbarth_ any ideas?
[16:49] <dbarth_> i've updated them, but we're now getting to the bug level
[16:49] <pitti> o/
[16:50] <skaet> thanks dbarth_ .  pitti go ahead
[16:50] <dbarth_> skaet: let me get back to you on the wi after the meeting
[16:50] <pitti> dbarth_: how much does current unity development rely on natty libraries/X.org?
[16:50] <pitti> i. e. woudl it be feasible to do the nvidia development/testing on maverick?
[16:50] <dbarth_> victorp: they are, but you need to ping lamalex to get them, it's the autopilot/testdrive module
[16:50] <pitti> or at least installing X.org 1.9 on natty?
[16:50] <dbarth_> pitti: well, we're running natty has you know
[16:50] <dbarth_> all of us
[16:51] <apw> pitti, i wondered if the xorg-retro thingy might be made to work for natty with the older ones in it
[16:51] <pitti> which is a good thing :) so perhaps natty with older X?
[16:51] <dbarth_> and we have a lot of nvidia users in the team
[16:51] <victorp> dbarth_,  thanks
[16:51] <dbarth_> so if the policy is to break nvidia because they're closed source, then you're breaking 50% of our dev machines...
[16:51] <apw> heh we're doing that to our users too
[16:52] <pitti> users> well, we were promised to get a build against current X in time for natty
[16:52] <pitti> dbarth_: would it help if we wrote a script/wiki page/etc to install 1.9 X.org on current natty and apt-pin it?
[16:52] <dbarth_> pitti: i fthere is a fallback plan, yes
[16:52] <pitti> some "wget from lauchpad/dpkg -i/create /etc/apt/preferences kind of thing
[16:52] <dbarth_> that would really help
[16:53] <dbarth_> or getting beta drivers earlier from nvidia
[16:53] <apw> dbarth_, oh have you tried the experimental gallium stuff ?
[16:53] <pitti> so the experimental nouveau 3D drivers don't work?
[16:53] <dbarth_> pitti: ted is on this
[16:53] <pitti> we even have a jockey handler for that these days
[16:53] <dbarth_> ie, reaching out to the xorg team or helping with a fallback plan
[16:53] <pitti> ok, cool
[16:54] <dbarth_> meaning, get in touch with him, so that you don't duplicate efforts
[16:54] <pitti> *nod*
[16:54] <dbarth_> i'll mention that on #ayatana
[16:54] <ogra> does that really help if you need to develop against the recent xorg version though ?
[16:54] <ogra> (rolling back i mean)
[16:55]  * ogra has the feeling the feature expectations might be to high if development can really only be done on the closed nvidia drivers instead of i.e. intel
[16:56]  * skaet notes that we're probably not going to be solving this here
[16:57] <skaet> time to more on...
[16:57] <skaet> [Topic] ARM team update - ogra
[16:57] <MootBot> New Topic:  ARM team update - ogra
[16:57] <ogra> o/
[16:57] <ogra> Status is at:
[16:57] <ogra> https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Natty
[16:57] <ogra> ..
[16:57] <ogra> Summary:
[16:57] <ogra>  - 705689 root cause was identified as gcc bug (kudos to janimo and NCommander for awesome tireless debugging work), a patch exists in the linaro gcc branch already but no test with a binary QT package from the archive has happened yet.
[16:58] <ogra>  - 2.6.38 tree was set up on git.ubuntu.com, a kernel package for OMAP 4 was uploaded to a PPA by the kernel team so we can do tests. A first patchset for getting the display driver is supposed to hit the tree next week.
[16:58] <ogra>  - WI work is still well going forward, workitems were shuffled around inside the team to get to a better balanced workload, the ARM thin client spec has been dropped.
[16:58] <ogra>  - QA work for better bug assignment strategy is currently going on
[16:58] <ogra>  - Work for upgrading bootloaders from commandline has started.
[16:58] <ogra>  - Last minor changes to the libqtdee and libqtgconf packages pending, once these are done all MIR team requirements for unity-2d should be fulfilled. Packages are to be seeded to the arm images by this weekend.
[16:58] <ogra> ..
[16:58] <ogra> Specs:
[16:58] <ogra> Entire status: http://people.canonical.com/~platform/workitems/natty/ubuntu-armel.html
[16:58] <ogra> Milestone: http://people.canonical.com/~platform/workitems/natty/ubuntu-armel-natty-alpha-3.html
[16:58] <ogra> Dropped: https://launchpad.net/ubuntu/+spec/other-arm-n-arm-thin-clients
[16:58] <ogra> ..
[16:58] <ogra> Serious Bugs:
[16:58] <ogra> bug 705689
[16:58] <ogra> the actual bugfix is waiting for the next gcc upload
[16:59] <ogra> but seems we have it done :)
[16:59] <ogra> ..
[16:59] <skaet> thanks ogra!   good to hear that the gcc bug has been found.
[17:00] <ogra> yeah, janimo and NCommander really deserve team beer :)
[17:00] <JamieBennett> \o/
[17:00] <ogra> and linaro was awesomely fast to add a proper fix ;)
[17:00] <skaet> :)
[17:00] <JamieBennett> beers all around ;)
[17:00] <ogra> :)
[17:01] <skaet> ogra, the dropped arm-thin-clients,  for alpha3 or entire release?
[17:01] <ogra> i postponed it to N+1
[17:01] <skaet> ogra,  thanks!
[17:01] <ogra> it trivial to implement for me as former ltsp upstream but i'm lacking the time
[17:01] <ogra> ..
[17:02] <skaet> [Topic] MOTU team update - ScottK
[17:02] <MootBot> New Topic:  MOTU team update - ScottK
[17:02] <ScottK> Nothing of significance to report.
[17:02] <ScottK> It'd be nice to have a final decision on Python 2.6/2.7 or 2.7 only for Natty.
[17:03] <ScottK> ...
[17:03] <skaet> Thanks ScottK,  what's the blockage on the decision?
[17:04] <ScottK> skaet: Someone making the decision.
[17:04] <ScottK> barry had a thread on u-devel recently, but no conclusion/decision AFAIK.
[17:05] <skaet> saw that thread,  ok will see if I can help get some resolution
[17:05] <ScottK> BTW, I think 2.7 only would be a bad idea.
[17:05] <wendar> barry, matthias and I are meeting next week to discuss
[17:05] <wendar> and, ScottK, I agree with your concerns
[17:05] <ScottK> Thanks.
[17:06] <skaet> wendar, you ok with taking an action to make sure a conclusion is posted to u-devel?
[17:06] <wendar> skaet: yes
[17:06] <skaet> wendar,  thanks!
[17:07] <skaet> [ACTION] wendar to post resolution on the Python 2.6/2.7 vs Python 2.7 inclusion in Natty
[17:07] <MootBot> ACTION received:  wendar to post resolution on the Python 2.6/2.7 vs Python 2.7 inclusion in Natty
[17:07] <skaet> [Topic] Linaro update - JamieBennett
[17:07] <MootBot> New Topic:  Linaro update - JamieBennett
[17:08] <JamieBennett> \o
[17:08] <JamieBennett> https://wiki.linaro.org/Releases/WeeklyReleaseMeeting/2011-02-10
[17:08] <JamieBennett> So, we have a few releases this week
[17:08] <JamieBennett> Linaro GDB 7.2 2011.02 released
[17:08] <JamieBennett> Linaro GCC 4.4 and 4.5 2011.02 released
[17:08] <JamieBennett> and Linaro QEMU
[17:09] <JamieBennett> not sure on whether doko will pick up the toolchain stuff for Ubuntu before FF or not at this stage
[17:09] <JamieBennett> probably too late but its there
[17:09] <JamieBennett> Bug wise we are in pretty good shape, nothing really for Ubuntu to worry about
[17:10] <skaet> ..?
[17:10] <JamieBennett> Our Alpha-2 gained another platform, Samsung Orion bringing our total to 7 architectures
[17:10] <JamieBennett> ..
[17:11] <skaet> Thanks JamieBennett!
[17:11] <skaet> I'll follow up with doko, when he returns next week, and see what the outlook is.
[17:11] <skaet> [ACTION] skaet follow up with doko after he returns on Linaro toolchain inclusion.
[17:11] <MootBot> ACTION received:  skaet follow up with doko after he returns on Linaro toolchain inclusion.
[17:12] <skaet> any other questions?
[17:12]  * skaet looks around...
[17:12] <skaet> [Topic] any other kudos/comments/questions?
[17:12] <MootBot> New Topic:  any other kudos/comments/questions?
[17:12] <skaet> going once...
[17:12] <skaet> twice...
[17:13] <skaet> thanks everyone!
[17:13] <skaet> #endmeeting
[17:13] <MootBot> Meeting finished at 11:13.
[17:13] <pitti> thanks everyone! and have a nice weekend
[17:13] <JamieBennett> thanks skaet
[17:15] <skaet> thanks pitti, JamieBennett, jibel, victorp, jdstrand, cjwatson, apw, zul, pitti, joshuahoover, Riddell, dbarth, ogra, ScottK,  appreciate your prep, and the details.  :)   Have a good weekend.
[17:15] <ogra> thanks skaet
[17:15] <jdstrand> skaet: thanks, you too :)
[17:15] <joshuahoover> thanks skaet!
[17:15] <jibel> thanks skaet, have a nice week end
[17:36] <apw> JFo, hey ... can you drop the 'kernel-tracking-bug' bugs from the tag search ... they are no use to the stable team so lets drop them
[17:38] <JFo> yep, can do