[16:00] <pitti> skaet: hi
[16:00] <pitti> skaet: would you mind if I go after QA today?
[16:01] <skaet> pitti,  sure.
[16:01] <pitti> skaet: silly me, I forgot to take my AC adapter with me, and I'm low on battery
[16:01] <skaet> on that note then...
[16:01] <Daviey> o/
[16:01] <skaet> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is skaet.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <skaet> [Topic] Oneiric Release Meeting overview - skaet_
[16:01] <skaet> .
[16:01] <skaet> Agenda is at:
[16:01] <skaet> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-06-09
[16:01] <skaet> The new agenda order we'll be trying out this week is in the meeting invite and in the team agenda.
[16:01] <MootBot> New Topic:  Oneiric Release Meeting overview - skaet_
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-06-09
[16:01] <skaet> .
[16:01] <skaet> Thank you to all who helped get Alpha 1 tested and published!
[16:01] <skaet> Release notes are at: https://wiki.ubuntu.com/OneiricOcelot/TechnicalOverview/Alpha1
[16:01] <skaet> Testing report can be found at: https://wiki.ubuntu.com/QATeam/ReleaseReports/OneiricAlpha1TestReport
[16:01] <skaet> .
[16:01] <skaet> Bugs targetted for this release can be found:
[16:01] <skaet> [LINK] https://bugs.launchpad.net/ubuntu/oneiric/+bugs
[16:01] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/oneiric/+bugs
[16:02] <skaet> Bugs milestoned for oneiric alpha 2 are at:
[16:02] <skaet> [LINK] https://launchpad.net/ubuntu/+milestone/oneiric-alpha-2
[16:02] <MootBot> LINK received:  https://launchpad.net/ubuntu/+milestone/oneiric-alpha-2
[16:02] <skaet> .
[16:02] <skaet> Events Approaching:
[16:02] <skaet> - Debian Import Freeze: June 30, 2011
[16:02] <skaet> - Oneiric Alpha 2: July 7, 2011
[16:02] <skaet> .
[16:02] <skaet> New site will be rolling out next week via email to ubuntu-devel to help with tracking topic areas in addition to teams (a bit more documentation is still needed)
[16:02] <skaet> Some of you may have seen the prototype over the last couple of weeks in prototype mode, and thank you for your help setting up topics and debugging.
[16:02] <skaet> [LINK]http://status.ubuntu.com/ubuntu-oneiric/
[16:02] <skaet> There's more info on it in the agenda, but I just wanted to say a big thank you to cjohnston!!
[16:02] <skaet> He's put in alot of hard work on putting the site together and getting the themes all in place, and the mechanisms debugged to make it possible.
[16:02] <MootBot> LINK received: http://status.ubuntu.com/ubuntu-oneiric/
[16:02] <skaet> .
[16:02] <skaet> Reminder:   please use ".." on separate line when you've finished typing.   If someone wants to comment during the updates, please "o/", so we know to wait.
[16:02] <skaet> questions?
[16:02] <skaet> ..
[16:03] <charlie-tca> o/
[16:03] <skaet> go charlie-tca
[16:04] <charlie-tca> Is the status wiki going to stay in java script? To see the charts, javascript must be enabled at this time.
[16:04] <charlie-tca> ..
[16:04] <skaet> charlie-tca, good question,  probably until we get it all debugged, then looking at moving may be an option.
[16:05] <pitti> also note that status.u.c. hasn't been officially annouced yet
[16:05] <pitti> it will be soon, when we have full confidence in it
[16:05] <skaet> yup,  you saw it here first folks.  :)
[16:05] <cjohnston> :-)
[16:05] <Daviey> (Some teams are already using it as their primary interface :/ )
[16:06] <skaet> Daviey,  yup and we appreciate those teams helping us debug it.  :)
[16:06] <charlie-tca> apparently, I don't have the right java in my browser, since I get all blank pages
[16:06] <Daviey> pitti: Are permissions going to be copied over, allowing people to edit the cfg's and run the commands you commented on?
[16:06] <skaet> charlie-tca, can you work with cjohnston off-line so he can see if he can reproduce what you're seeing?
[16:07] <pitti> Daviey: that's still TBH
[16:07] <pitti> TBD
[16:07] <charlie-tca> sure
[16:07] <Daviey> ok
[16:07] <pitti> Daviey: we quickly talked with jpds, but we'll probably use a ~platform bzr branch which they pull in
[16:07] <Daviey> Ok, groovy.
[16:08]  * skaet looks around for other questions?
[16:08] <skaet> ok, heading into the round table then.
[16:08] <ScottK> o/
[16:08] <ScottK> More of a comment.
[16:08] <skaet> ok ScottK
[16:09] <ScottK> I think Kubuntu will be moving to using work items like other teams do.
[16:09] <ScottK> Personally, I liked the wiki, but i got outvoted.
[16:09] <ScottK> You might chat with apachelogger about helping get Kubuntu stuff properly sync'ed.
[16:09] <ScottK> ..
[16:09] <skaet> Thanks ScottK,  will do my best to help make the transition smooth.
[16:10] <skaet> and will talk to apachelogger.  :)
[16:10] <ScottK> He's rushing to catch a train ATM, but later I'm sure he'll be glad to help.
[16:10] <ScottK> (best time to volunteer people for stuff)
[16:11] <skaet> :)  Any other teams interested in setting up topics for tracking things,  just let me, cjohnston or wendar know, and we'll try to help.
[16:11] <skaet> back to the round table...
[16:11] <skaet> [Topic] Toolchain update - doko
[16:11] <MootBot> New Topic:  Toolchain update - doko
[16:11]  * skaet looks around for doko_ 
[16:12] <skaet> if folks could look at the links on the agenda,  the Failures to Build are still pretty high for main.
[16:13] <skaet> [Topic] QA team update -  jibel
[16:13] <MootBot> New Topic:  QA team update -  jibel
[16:13] <cjwatson> 15:49 <doko_> cjwatson: re-uploaded, now afk
[16:13] <cjwatson> I guess he's not around
[16:13] <skaet> thanks cjwatson
[16:13] <jibel> hi all!
[16:13] <skaet> :)
[16:13] <jibel> * Bootchart Metrics and desktop testing not started. It will be discussed at the automation testing sprint next week.
[16:14] <jibel>  * Automatic Upgrade Testing:
[16:14] <jibel> http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:14] <MootBot> LINK received:  http://people.canonical.com/~mvo/automatic-upgrade-testing/current/
[16:14] <jibel>  * ubuntu and xubuntu failed: bug 781076
[16:14] <jibel>  * kubuntu fails: conflict file between plasma-dataengines-workspace 4:4.6.2a-0ubuntu5.1 and kdebase-workspace-bin 4:4.6.3-1ubuntu3
[16:14] <jibel> * Top 5 packages with most bugs reported during last week:
[16:14] <jibel> unity-2d: mostly crashers fixed with qt4-x11 update.
[16:15] <jibel> lightdm
[16:15] <jibel> doc-base: see bug above
[16:15] <jibel> gnome-user-share: bug 788714
[16:15] <jibel> unity
[16:15] <jibel> == Results of Alpha 1 ISO Testing ==
[16:16] <jibel> The main issues found are:
[16:16] <jibel>  * unity-2d crashes which is a problem between gcc 4.6 and qt4-x11 violating strict aliasing rules.
[16:16] <jibel>  * gnome-user-share crash: need porting to gtk3: fixed
[16:16] <jibel>  * nautlius background not redrawing
[16:16] <jibel>  * missing windows buttons: Fixed
[16:16] <jibel>  * No USB support on beagle/beagleXM
[16:16] <jibel>  * Oneiric Alpha1 Server x86 and x86_64 RAID1 Test Failed
[16:16] <jibel>  * Ubiquity on Kubuntu failed to run
[16:16] <jibel> Very few installer and Unity bugs. But since most testers are running VMs, unity received little testing compared to unity-2d.
[16:16] <seb128> ("  * nautlius background not redrawing" should be fixed as well)
[16:16] <pitti> unity-2d crash should also be fixed now with latest qt?
[16:17] <seb128> (we have the key correctly set to get nautilus displaying the background by default and the url has been fixed as well)
[16:17] <ScottK> pitti: Yes.
[16:18] <jibel> pitti, right. the qt4-x11 updated fixed most of unity-2d crashers
[16:18] <jibel> seb128, right. must be fixed, but didn't verified yet
[16:19] <jibel> There are still 10 bugs marked as new to triage:  http://tinyurl.com/63wkemt
[16:19] <jibel> so please pick yours.
[16:19] <ScottK> jibel: On Kubuntu ubiquity would run a live session fine, just not do an installation.
[16:19] <cjwatson> maco posted a branch for half of the problem which is pending review.  I've been having ADSL line rate issues so haven't managed to pull down a test image yet
[16:20] <jibel> this is bug 791446
[16:21] <jibel> The laptop tracker for Oneiric is opened. Time to test alpha 1 on real iron.
[16:21] <jibel> https://lists.ubuntu.com/archives/ubuntu-qa/2011-June/001615.html
[16:21] <jibel> Next community testing milestones:
[16:21] <jibel> Alpha 2 testing will start on July 5th
[16:21] <jibel> Followed by a week of ATI/nVidia proprietary driver testing
[16:21] <jibel> and 10.04.3 the week after.
[16:21] <jibel> ..
[16:22] <skaet> Thanks jibel!  :)
[16:22] <skaet> Some very good data in there,  will digest the detail after the meeting.
[16:22] <skaet> anyone else have specific questions right now?
[16:22] <skaet> [Topic] Desktop team update - pitti
[16:22] <MootBot> New Topic:  Desktop team update - pitti
[16:23] <pitti> GNOME 3 is mostly in oneiric now, with the exception of smaller things like the system monitor; we still lack an Ubuntu-ish theme, but that's being developed by DX; some of it is also blocked by some MIRs like accountsservice
[16:23] <pitti> Default login manager now switched to lightdm
[16:23] <pitti> Alpha-2 work items: http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team-oneiric-alpha-2.html → we are behind the trend line, but we expect some faster progress soon; not too much of a concern just yet
[16:23] <pitti> CD space situation: We worked hard on downsizing, and cut off 30 MB, so that most of the daily images are now within limits, except i386 alternate (705 MB); we expect 4.5 MB growth from new X.org gallium drivers with new LLVM, and potential growth of ~ 6 to 10 MB for thunderbird (not firmly decided yet)
[16:23] <pitti> RC bugs: we do have a few well-known problems from the GNOME 3 transition, but nothing earth shattering right now; details are at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus#rcbugs
[16:23] <pitti> ..
[16:23] <pitti> oh, breaking news: latest lsb upload pulls in python 3 (another +6 MB)
[16:24] <pitti> so it's really high time to drop python 2.6 now
[16:24] <pitti> to make up for the space, and not ship 3 python versions
[16:24] <ScottK> o/
[16:24] <pitti> ..
[16:24] <skaet> go ScottK
[16:24] <ScottK> I think lsb pulling in python3 should be investigated.  That sounds wrong.
[16:24] <pitti> it might have been ported?
[16:25] <seb128> doko just switched it to python3
[16:25] <pitti> but anyway, even if it's wrong, there'll be sooner or later a package which uses py3
[16:25] <ScottK> Given the number of 2.7 related issues we're still digging through in Debian, I think dropping 2.6 is premature.
[16:25] <ScottK> ..
[16:25] <ScottK> Sure.
[16:25] <pitti> I really really object to 3 python versions on the CD
[16:25] <ScottK> I agree.
[16:25] <seb128> pitti, wasn't there some discussion about keeping python3 out of the CD for this cycle?
[16:25] <ScottK> The issue is which two.
[16:25] <ogra_> python1 !
[16:25] <ScottK> (for the moment)
[16:25] <pitti> if we really need 2.6 (I don't think we do, though), can we postpone py3 for the next release?
[16:25] <ogra_> surely the smallest ;)
[16:25] <cjwatson> I don't think we need to panic about lsb; it doesn't merit immediate reversion or anything
[16:25] <pitti> seb128:  it was proposed
[16:26] <ScottK> I think we'll drop 2.6 before FF.
[16:26] <ScottK> I'd be suprised if we don't.
[16:26] <cjwatson> I don't mind oversizedness that's projected to go away by FF
[16:26] <pitti> I thought the main issue here was to help Debian to switch to 2.7, right?
[16:26] <cjwatson> as long as we know how
[16:27] <pitti> I also have a few projects which could also use py3
[16:27] <ScottK> pitti: Yes.
[16:27] <pitti> I just didn't want to be the one to introduce the dependency first, but now that we have it, a more firm plan would be good
[16:27] <pitti> i. e. if we want to do some more py3 porting in oneiric, it would certainly be better than starting with it in the lts?
[16:27] <ScottK> That's the intent.
[16:28] <pitti> *nod* thanks
[16:28] <pitti> sounds like a plan then
[16:28] <pitti> thanks for letting me go first today; I need to go offline now, running out of battery :/
[16:28] <skaet> Thanks pitti! :)  any other questions?
[16:28] <skaet> [Topic] Hardware Certification team update
[16:28] <skaet> team will be restarting certification runs in next couple of weeks.  No data yet.
[16:28] <MootBot> New Topic:  Hardware Certification team update
[16:29]  * pitti waves
[16:29]  * skaet waves back - thanks again.
[16:30] <skaet> [Topic] Security team update - jdstrand
[16:30] <MootBot> New Topic:  Security team update - jdstrand
[16:30] <jdstrand> hi
[16:30] <skaet> :)
[16:30] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Oneiric
[16:30] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Oneiric
[16:30] <jdstrand> [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-security.html
[16:30] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/oneiric/canonical-security.html
[16:30] <jdstrand> We are currently on track for blueprints, and thanks to mdeslaur apparmor no longer requires perl on the install images.
[16:30] <jdstrand> Our team is mostly concentrating on updates atm, and getting to work items as we can fit them in.
[16:31] <jdstrand> Looking at the (rather long) list of oneiric bugs, I don't see anything worth highlighting here.
[16:31] <jdstrand> I've heard that unity-2d doesn't work too well in oneiric with any of the video drivers. unity doesn't run in kvm (our standardized virtualization technology, with a ton of scripting and tools around it).
[16:31] <jdstrand> (kvm video drivers)
[16:31] <jdstrand> This is a major concern for the security team as without good VM support for unity-2d, we can't test applications in a default install. In natty 'vmvga' seems to work ok. This is bug 759803 and bug 792075.
[16:31] <skaet> dbarth, ^^
[16:32] <jdstrand> I've just commented in 792075 about some findings from our team, but I wanted to highlight this
[16:32] <jdstrand> (things may be more positive now)
[16:32] <jdstrand> I've added these to our list of bugs we're interested in from other teams
[16:32] <jdstrand> ..
[16:33] <skaet> Thanks jdstrand!  :)
[16:33] <jdstrand> oh, also 792075 is in a weird state wrt subscribers (there are none)
[16:33] <jdstrand> (besides the reporter and out team, who I just added)
[16:33] <skaet> hmm...
[16:34] <seb128> jdstrand, wasn't the kvm issue the qt bug that got fixes this week?
[16:34] <skaet> jibel, bdmurray,  ^^  can you look into the bug state of 792075 after the meeting with me?
[16:35] <jdstrand> seb128: mdeslaur indicated upgrading seems to make things work again. he (or me) will test the daily and see if things are better there
[16:35]  * dbarth is checking
[16:36] <skaet> ok,  if no more questions,  we'll let the investigation happen asynch and move on.
[16:36] <dbarth> skaet: a qt issue as indicated in the comments
[16:36] <skaet> dbarth, thanks.
[16:36] <skaet> [Topic] Kernel team update - ogasawara
[16:36] <MootBot> New Topic:  Kernel team update - ogasawara
[16:36] <ogasawara> 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:36] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[16:36] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team-oneiric-alpha-2.html
[16:36] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team.svg
[16:36] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric
[16:36] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team-oneiric-alpha-2.html
[16:37] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team.svg
[16:37] <ogasawara> The biggest news recently is that Linus has decided to bump the upstream kernel version to v3.0.  This means that instead of Oneiric targetting a v2.6.40 kernel, we will use v3.0.  The move from a 3 digit version (eg 2.6.y) to a 2 digit version (eg 3.x) did cause breakage for scripts and packages expecting a 3 digit version.  We fixed what was known and uploaded an Oneiric kernel based on the latest v3.0-rc2 upstream relea
[16:37] <ogasawara> se.  We took extra care for how we versioned our package should we choose to move back to a 3 digit version scheme.  We've unfortunatley however just discovered that libc6 is having issues installing with the newer 2 digit version.  We're actively investigating.  Subsequently we're holding off on uploading linux-meta-3.0 until the libc6 install issue is resolved.
[16:37] <ogasawara> Of the bugs called out in the agenda, status is as follows:
[16:37] <NCommander> o/
[16:37] <ogasawara> 754744 - Assigned to kernel dev and under investigation.  Also forwarded to upstream but no response yet.
[16:37] <ogasawara> 542660 - Assigned to kernel dev.  Recent comments indicate possible workaround.  Confirmation is still needed against Oneiric.
[16:37] <ogasawara> 760131 - A patch has landed in 2.6.39.1 upstream stable which has been applied to and tested with a 2.6.38 Natty test kernel.  It has been confirmed that power consumption is indeed lower than what was released in 2.6.38.  It is not clear however if this is an actual fix for the noted regression or just an overall power management improvement which has landed.  Regardless we'll work to get this patch pushed through as an S
[16:37] <ogasawara> RU.  Unfortunately it appears the bug is starting to get dog piled with drive by commenters. :(
[16:37] <ogasawara> Questions?
[16:38] <ogasawara> ..
[16:38] <cjwatson> eglibc should be easy to sort out ...
[16:38] <skaet> Thanks ogasawara!  :)
[16:38] <cjwatson> is there a bug number for that?
[16:38] <skaet> go NCommander
[16:38] <ogasawara> cjohnston: no bug number, apw was digging into it
[16:38] <NCommander> Since several ARM kernels are still 2.6.3x for now and the probably for quite awhile, will there be ongoing care to make sure the scripts can handle 2.6 or 3.0?
[16:38] <ogasawara> bah, cjwatson ^^
[16:39] <ogra_> NCommander, several ?
[16:39] <ogra_> only omap4
[16:39] <ogasawara> NCommander: we'll make a note to check
[16:39] <cjwatson> NCommander: everything I've seen so far has been fixed to handle both
[16:39] <NCommander> ogra_: Linaro's kernel package is still 2.6 last I checked.
[16:39] <NCommander> cjwatson: just making sure. didn't want to have an oh **** issue down the line
[16:39] <NCommander> ..
[16:39] <ogra_> NCommander, linaros kernel packages dont get updates per policy
[16:40] <cjwatson> the installer will need some changes for 3.0 too; I'll be working on those now I have test packages
[16:40] <ogra_> (no security, no SRUs)
[16:40] <apw> cjwatson, if i am honest i wouldn't start too soon on changes for the new kernel
[16:40] <ScottK> ogra_: Don't get updated by the security/kernel teams, but someone could prepare updates if they were motivated.
[16:40] <ogra_> ScottK, suuure :)
[16:41] <apw> cjwatson, it is not at all clear linus won't throw in the towel and call it 3.0.0 cause of other userspace interactions
[16:41] <apw> cjwatson, i am trying to get a definative answer before doing much more
[16:41] <cjwatson> heh, eglibc build kind of breaks too
[16:41] <apw> cjwatson, yeah i notived, and actually so does the install of it ... my test box is a heap as a result
[16:42] <apw> cjwatson, so far i have held off on the meta package as a result
[16:42] <cjwatson> eglibc build should only break if your build system is actually running 3.0 though, which the buildds won't for a while
[16:42]  * skaet thinks the questions have stopped,   so moving on.  :)
[16:42] <skaet> [Topic] Foundations team update - cjwatson
[16:42] <MootBot> New Topic:  Foundations team update - cjwatson
[16:43] <cjwatson> Feature progress this week:
[16:43] <cjwatson>  * foundations-o-application-sandboxing underway: Arkose rewritten in Python and converted to LXC
[16:43] <cjwatson>  * multiarch bootstrapped in Debian to the point where libraries can be converted to it, which should start reducing our patch stack soon (full dpkg support is still pending review though)
[16:43] <cjwatson>  * foundations-o-live-build down to the last handful of small work items
[16:43] <cjwatson>  * desktop-o-gtk3-gnome3: ubiquity mostly converted to PyGI, though blocked on porting a custom widget (timezone map)
[16:43] <cjwatson>  * foundations-o-ubiquity: design work on installation failure metrics; seems rather closer to a consensus now
[16:43] <cjwatson>  * packageselection-foundations-n-event-based-initramfs: working on upstartified way to switch root filesystem; most review comments addressed
[16:43] <cjwatson>  * foundations-o-better-apport-package-bugs: prevented reporting of bugs due to missing packages in apt cache; wrote some apport bug patterns for foundations-bugs
[16:43] <cjwatson>  * upstart: lots of upstream merging, with lp:upstart getting back into a properly synchronised state again; discussing oneiric plans on mailing lists
[16:43] <cjwatson>  * foundations-o-apt-mirror-method: initial progress on required apt changes
[16:43] <cjwatson>  * software-center: merged basic QML UI
[16:43] <cjwatson>  * foundations-o-python-versions: 3.1 reverse-dependencies eradicated; working on Python 3 disk usage data for CDs
[16:43] <cjwatson>  * python: released 2.6.7
[16:43] <cjwatson> ..
[16:43] <cjwatson> (I didn't comment on bugs, there aren't many on our agenda at the moment and we're well off alpha 2, so happy to let those run for a while)
[16:44] <cjwatson> (so ask if there are any you particularly care about)
[16:44] <skaet> thanks cjwatson.  :)
[16:44] <skaet> will follow up on the bugs then offline.
[16:44] <skaet> looks like a pretty productive week.  :)
[16:44] <skaet> any questions?
[16:44] <skaet> [Topic] Server team update - Daviey
[16:44] <MootBot> New Topic:  Server team update - Daviey
[16:44] <Daviey> Hello!
[16:44] <skaet> :)
[16:45] <Daviey> Another short one this week.
[16:45] <Daviey> Alpha 1 incoming bug count is low (as expected due to low exposure).  ISO testing didn't raise anything unexpected.
[16:45] <Daviey> Current burn down charts are looking on target (both full cycle and A2).  Not all deliverables that will be completed for A2 are yet marked such).
[16:45] <Daviey> No current wider concerns.
[16:45] <Daviey> I do need to talk to foundations (probably cjwatson) early next week about some of our ISO changes planned.
[16:45] <Daviey> We have a mountain of MIR's we need to undertake this subcycle.  So i suspect ~ubuntu-server need to buy ~ubuntu-mir plenty of beer.
[16:45] <Daviey> We are currently working with Canonical SI team for many of the Orchestra deliverables.
[16:45] <Daviey> I do have concerns that the decision to use ~ubuntu-server is attaching some WI's to our team view that should not belong there, for example: other-n-security-kernel
[16:45] <Daviey> ...
[16:46] <skaet> Thanks Daviey!  :)
[16:46] <Daviey> no, thank you :)
[16:46] <skaet> any questions?
[16:46] <skaet> [Topic] ARM team update - ogra_
[16:46] <MootBot> New Topic:  ARM team update - ogra_
[16:46] <ogra_> yay, thats me :)
[16:46] <skaet> :)
[16:47] <ogra_> Full status is at https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Oneiric
[16:47] <ogra_> -
[16:47] <ogra_> Summary:
[16:47] <ogra_>  * More work on preparing the tegra ac100 port was done (thanks to GrueMaster for hours of debugging).
[16:47] <ogra_>  * Netinstall images for omap3 and 4 were created (as part of the server implementation)
[16:47] <ogra_>  * The netbook images were dropped in favour of preinstalled desktop images.
[16:47] <ogra_>  * We welcome infinity as a new team member !
[16:47] <ogra_>  * The first patches for performance optimization of our SD card images have been produced and will land in the image build system soon.
[16:47] <ogra_> -
[16:47] <ogra_> Images:
[16:47] <ogra_>  * Desktop images surprisingly seem to build out of the box
[16:47] <ogra_>  * Headless/serial images build fine.
[16:47] <ogra_> -
[16:47] <ogra_> Spec work:
[16:47] <ogra_>  * Entire http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html
[16:47] <ogra_>  * A2 http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-oneiric-alpha-2.html
[16:47] <ogra_>  (how do we get our team onto status.ubuntu.com ?)
[16:47] <ogra_> -
[16:47] <ogra_> Serious Bugs:
[16:47] <ogra_>  * bug 794938 [oneiric] lightdm crashes on armel
[16:47] <ogra_>  * bug 791552 [oneiric] USB support broken on omap3
[16:47] <ogra_> ..
[16:48] <skaet> Thanks ogra_ !  :)   (and welcome infinity )
[16:48] <skaet> can someone get 791552 prioritized so it shows up as a serious bug,  looks like its undefined right now...
[16:49] <ogra_> will do
[16:49] <ScottK> o/
[16:49] <skaet> thanks ogra_ ! :)
[16:49] <skaet> ScottK go
[16:49] <ScottK> Any word on if we'll have an armhf port this cycle?
[16:49] <ScottK> ..
[16:50] <ogra_> linaro stuff ...
[16:50] <ogra_> not sure where we stand yet
[16:50] <ScottK> OK.
[16:51] <ogra_> but i can find out and report next week :)
[16:51] <skaet> ogra_, can you work fabo to figure it out?
[16:51] <Daviey>  
[16:51] <skaet> lol
[16:51] <ogra_> snap :)
[16:51] <skaet> thanks ogra_ :)
[16:52] <skaet> Daviey, you have a comment/questions?
[16:52] <skaet> hmm... guess not.  ok,  moving on.
[16:52] <skaet> [Topic] Desktop Experience Team Update - dbarth
[16:52] <MootBot> New Topic:  Desktop Experience Team Update - dbarth
[16:53] <dbarth> hiya
[16:53] <skaet> :)
[16:53] <dbarth> i have prepared notes for the meeting at https://wiki.ubuntu.com/DesktopExperienceTeam/OneiricReleaseStatus
[16:53] <dbarth> essentially, we have a couple of sru fixes ready and delivered between this week and next monday
[16:53] <dbarth> incl. the display garbled problem
[16:54] <dbarth> https://wiki.ubuntu.com/DesktopExperienceTeam/OneiricReleaseStatus#preview
[16:54] <dbarth> for oneiric, we're reaching the end of the 1st iteration of development
[16:54] <dbarth> with unity updates (see notes, compiz mostly for the moment, but there should be a new shared lib by next week)
[16:55] <dbarth> a new appindicator module for qt, along with unity-2d updates (gap reduction with the GL version)
[16:55] <dbarth> a few indicators and theme related progresses; the rest is mostly infrastructure that will bear fruit next iteration
[16:55] <dbarth> and a batch of touch updates
[16:56] <ScottK> o/
[16:56] <dbarth> that will let eog/evince and qt apps work with the touch stack that went into natty
[16:56] <dbarth> ...
[16:56] <skaet> Thanks dbarth! :)   Will be plotting your revised landings dates against the interlock schedule and let you know offline if I see issues.
[16:56] <skaet> any questions for dbarth ?
[16:56] <dbarth> skaet: right, forgot that, but that was in the notes
[16:57] <dbarth> yup? ScottK?
[16:57] <ScottK> It's not clear how well synchronized the appindicator module for Qt is with upstream plans.  We need to make sure we allow time in the schedule to get that part sorted correctly.
[16:57] <ScottK> ..
[16:57] <dbarth> yeah, they were interested, but not ready to take that in their own roadmap
[16:58] <ScottK> So much like the appmenu work we need to build a bridge that will get us there.
[16:58] <dbarth> the module agateau prepared is a plugin that is independant of the qt code base; just plugs into known interfaces
[16:58] <dbarth> agreed
[16:58] <ScottK> There's a core Qt patch to make the plugin work.
[16:58] <ScottK> That's the part I'm most worried about.
[16:58] <dbarth> ah, that part was not sold to me yet ;)
[16:58] <dbarth> i'll double check with you and agateau
[16:59] <ScottK> Thanks.
[16:59] <skaet> any other questions?
[16:59] <ScottK> We discussed it yesterday or the day before.
[16:59] <dbarth> ok
[16:59] <skaet> [Topic] Kubuntu Team update - ScottK
[16:59] <MootBot> New Topic:  Kubuntu Team update - ScottK
[17:00] <ScottK>  * Alpha 1 live CD runs a session, but won't install (already discussed)
[17:00] <ScottK>  * ISO size issues resolved after Alpha 1
[17:00] <ScottK>  * Component mismatches all worked out too
[17:00] <ScottK>  * Coordinating Qt updates with Desktop team
[17:00] <ScottK>    - Need to make sure things (like touch patches) land with enough time for upstream review
[17:00] <ScottK>  * KDE merges from Debian are ~done, starting to work on KDE 4.7.
[17:00] <ScottK>  * KDE upstream issues with tarball splits (following move from svn to git) seem largely resolved for this cycle
[17:00] <ScottK> ..
[17:00] <seb128> ScottK, didrocks said he would try to get the qt appindicator thing sorted next week during the qt contributor summit
[17:00] <ScottK> seb128: Yes.  That's what we discussed.
[17:00] <ScottK> (I recall now that you remind me)
[17:01] <ScottK> ..
[17:01] <skaet> Thanks ScottK!  :)
[17:02] <skaet> we've talked about one of the bugs on the agenda,  but is there any update on bug:794320?
[17:02] <ScottK> Which one is that?
[17:03] <skaet> .desktop files not being translated
[17:03] <ScottK> Being worked.
[17:03] <ScottK> I think it's close.  Should be no problem for Alpha 2.
[17:03] <skaet> coolio.  thanks.
[17:03] <skaet> any other questions?
[17:03] <debfx> most .desktop files are translated, it only affects for example notifications
[17:04] <skaet> ok,  thanks.  :)
[17:04] <skaet> [Topic] Linaro update - fado
[17:04] <MootBot> New Topic:  Linaro update - fado
[17:04] <ScottK> skaet: fabo?
[17:04] <skaet> sigh,  ... sorry,  fabo
[17:04] <skaet> yup
[17:05] <skaet> is fabo around?   its getting late for him...
[17:05] <fabo> yes, I'm around
[17:05] <skaet> :)
[17:05] <skaet> any updates from Linaro?  (toolchains,  kernel versions,  etc.  ;) )
[17:06] <fabo> we're working on our monthly release
[17:06] <fabo> a toolchain update is planned with a release ever 3rd thursday of the month
[17:07] <fabo> linaro-2.6.39 kernel repository opened
[17:08] <fabo> john rigby is working on the packaging
[17:09] <fabo> our platform team will release the last thursday of each month, including all goodies from our WGs (toolchain kernel)
[17:09] <fabo> they'll release on latest stable Ubuntu (natty)
[17:09] <fabo> in parallel, we planned to provide developers build for oneiric
[17:10] <fabo> ..
[17:10] <skaet> Thanks fabo! :)
[17:10] <fabo> questions? :)
[17:10] <skaet> When do you plan on forking the stable toolchain branch?
[17:11] <james_w> it's not confirmed to be happening yet, but I would imagine soon if it does happen
[17:11] <fabo> it's under discussion. Michael Hope has send a mail about it. The plan will be clear on next week.
[17:12] <skaet> thanks james_w, fabo - will follow up on the thread then.
[17:12] <skaet> any other questions?
[17:13] <skaet> do we have anyone here from Edubuntu, Xubuntu, Ubuntu Studio, Mythbuntu, that has questions?
[17:13] <skaet> or status to share?
[17:14] <skaet> [Topic] MOTU team update - tumbleweed
[17:14] <MootBot> New Topic:  MOTU team update - tumbleweed
[17:14] <tumbleweed> hi
[17:14] <skaet> :)
[17:14] <tumbleweed> not too much to report:
[17:14] <tumbleweed> GHC transition almost done, many of the others still have some way to go.
[17:14] <tumbleweed> fair number of merges outstanding (and thus missing RC fixes), more than this point last cycle according to the graphs
[17:14] <tumbleweed> *lots* of FTBFS, far more than I'd like.
[17:14]  * skaet nods
[17:14] <tumbleweed> nigelb has someone preparing a list of toolchain related ones to request help for
[17:14] <tumbleweed> the bugs mentioned on the agenda are mostly milestoned FTBFSs, won't repeat them here
[17:14] <tumbleweed> ..
[17:15] <skaet> Thanks tumbleweed!  :)
[17:15] <skaet> There's a fair number of FTBFS marked as New against A2 in the A2 milestone bug list.   Should they be considered confirmed at this point?
[17:16]  * tumbleweed hadn't seen those until I looked at the agenda
[17:17] <tumbleweed> I assume doko is doing some (semi-?)automated filing
[17:17] <skaet> yes,  but doesn't seem to be automated fixing going on ;)
[17:17] <skaet> they've been lingering
[17:17] <tumbleweed> yeah
[17:18] <skaet> can we get together offline and see if we can figure out a way to track them better, and see if we can get help lined up.
[17:18] <skaet> ??
[17:18] <tumbleweed> I'm not too concerned about tiher status, new vs confirmed. Looking at the bug log is half the way to fixing most of them
[17:18] <tumbleweed> sure
[17:18] <tumbleweed> err build log
[17:18] <skaet> thanks.
[17:18] <skaet> :)
[17:18] <skaet> any other questions for tumbleweed?
[17:19] <skaet> [Topic]  any other questions,  comments?
[17:19] <MootBot> New Topic:   any other questions,  comments?
[17:20]  * skaet notes that Ubuntu One is at a sprint this week,  and their status will be updated early next week.
[17:20] <skaet> ok,  looks like that's it then for this week.
[17:20] <Daviey> \o/
[17:20] <skaet> Thank you all.
[17:20] <skaet> #endmeeting
[17:20] <MootBot> Meeting finished at 11:20.
[17:21] <charlie-tca> Thanks, skaet
[17:21] <ScottK> tumbleweed: I think FTBFS bugs are generally just noise and we should avoid them unless they add particular value (e.g. some hint about how to fix it).
[17:22] <skaet> thank you  jibel, jdstrand, ogasawara, cjwatson, Daviey, ogra_,  dbarth, charlie_tca,  ScottK,  fabo, seb128, pitti, tumbleweed
[17:22] <ogra_> thanks skaet
[17:22] <seb128> thanks skaet
[17:22] <jibel> Thanks skaet
[17:22] <jdstrand> thanks skaet
[17:22] <fabo> thanks skaet
[17:23] <tumbleweed> ScottK: I tend to agree. I test-build the package before trying to fix it
[17:42] <chattr> clipit
[17:46] <chattr> sorry, wrong channel
[17:47] <apachelogger> skaet, ScottK: the only missing thing for topics should be a spec for left-overs, syncing wiki progress to specs and setting kubuntu-members as assignee for unassigned items
[17:50] <skaet> apachelogger, :)  excellent.
[20:03] <cjohnston> apachelogger: if you need help with any of that, let me know