[15:56] <marjo> hi skaet
[15:56] <skaet> hi marjo  :)
[15:59] <jdstrand> o/
[16:00] <seb128> hi
[16:00] <ScottK> \o
[16:00] <ttx> o/
[16:01] <skaet> hi all,   feels about time to start.   anyone else we're waiting for?
[16:01] <cjwatson> hi
[16:01]  * ScottK votes start on time and let people catch up as needed.
[16:01]  * skaet thinks that sounds good.
[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:02] <skaet> [TOPIC] 10.10
[16:02] <MootBot> New Topic:  10.10
[16:02] <skaet> any updates from dyfet on the open actions?
[16:02] <skaet> https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-08-27
[16:02] <ScottK> skaet: Got patches from NCommander and Riddell, so it's OBE.
[16:03] <ScottK> (the KDE one)
[16:03] <skaet> ScottK,  thanks.   will stop carrying it forward then.
[16:03] <ScottK> In fact KDE 4.5 is now fully built on armel for the first time.
[16:03] <ttx> ScottK: \o/
[16:03] <skaet> :)
[16:04] <skaet> will it be going out with 10.10 beta?
[16:05] <ScottK> We should have images, but Kubuntu on armel isn't a primary target for that architecture.
[16:05] <skaet> ScottK,  ok.
[16:06] <skaet> [TOPIC] QA team report
[16:06] <MootBot> New Topic:  QA team report
[16:06] <marjo> Hardware testing
[16:06] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo> Laptops:
[16:06] <marjo>      Passed:   41 (85%)    Failed:    1 ( 2%)    Untested:  6 (13%)
[16:06] <marjo>  Servers:
[16:06] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:06] <marjo>      Passed:   58 (85%)    Failed:    0 ( 0%)    Untested: 10 (15%)
[16:06] <marjo>  Netbooks:
[16:06] <marjo>      Passed:   12 (75%)    Failed:    0 ( 0%)    Untested:  4 (25%)
[16:06] <marjo>  Desktops:
[16:06] <marjo>      Passed:   11 (79%)    Failed:    0 ( 0%)    Untested:  3 (21%)
[16:07] <marjo> Boot Performance
[16:07] <marjo> http://people.canonical.com/~ameetp/BootChart.html
[16:07] <marjo> Per robbiew's request, the report now separates UNE and Desktop.
[16:07] <marjo> Kbuntu will be added next.
[16:07] <marjo> Boot Performance Week of 2010-08-23 to 2010-08-27
[16:07] <marjo> -------------------------------------------------
[16:07] <MootBot> LINK received:  http://people.canonical.com/~ameetp/BootChart.html
[16:07] <marjo> Number of system regressions on Ubuntu Desktop: 0
[16:07] <marjo> Number of system regressions on Ubuntu Netbook Edition: 0
[16:07] <marjo> ScottK:  Kbuntu will be added next.
[16:07] <ScottK> Great.
[16:08] <marjo> # Milestoned Features
[16:08] <marjo> * qa-maverick-mago-daily - postponed to end of release, due to higher priority tasks
[16:08] <marjo> https://blueprints.launchpad.net/ubuntu/+spec/qa-maverick-mago-daily
[16:08] <marjo> skaet: that's all from QA team
[16:08] <skaet> marjo,  thanks!
[16:09] <skaet> any particular concerns as we head into beta next week?
[16:10] <marjo> skaet: none at this time; sent out reminders for ISO testing
[16:10] <skaet> cool.  thanks.   any other questions for QA?
[16:10] <skaet> [TOPIC] security team
[16:10] <MootBot> New Topic:  security team
[16:11] <jdstrand> hi
[16:11] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:11] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Maverick
[16:11] <jdstrand> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-security.html
[16:11] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-security.html
[16:11] <jdstrand> We currently have no milestoned bugs.
[16:11] <jdstrand> We are waiting for feedback on the openssl and related packages in -proposed for security-m-tls-renegotiation-updates, our last remaining essential blueprint.
[16:11] <jdstrand> Work on arm-m-missing-security-features is ongoing.
[16:12] <jdstrand> Hope to release ufw 0.30 and get it into maverick for beta. We have a pre-release of 0.30 in maverick now, and this would be a pure bugfix upload-- fixes a couple packaging issues as well as several IPv6 bugs. See SecurityTeam/ReleaseStatus/Maverick for details.
[16:12] <jdstrand> that may have to wait til after beta
[16:12] <jdstrand> Getting upstream apparmor userspace 2.5.1 together is ongoing, which is something that we will want in Maverick, but not beta. It has many fixes for the userspace tools to work with our maverick (and upstream) kernel
[16:13]  * skaet makes a note to keep an eye open for ufw 0.30
[16:13] <jdstrand> that's pretty much it from me
[16:13] <skaet> nice.
[16:13] <skaet> any questions?
[16:14] <skaet> [TOPIC] kernel team
[16:14] <MootBot> New Topic:  kernel team
[16:14] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:14] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[16:14] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:14] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team-ubuntu-10.10-beta.html
[16:14] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.svg
[16:14] <ogasawara> All our specs/blueprints for Beta are complete.
[16:14] <skaet> sweet.
[16:14] <ogasawara> On the bugs noted in the agenda, status is as follows:
[16:14] <ogasawara> Bug 605488 - After speaking with ogra and GrueMaster, we're closing this bug for now as no one is able to reproduce the issue any more.  Should this re-appear the bug will be re-opened.
[16:14] <ogasawara> Bug 605739 - Believed to be resolved in the latest linux-ti-omap4-2.6.34-903.7 kernel.  Still waiting for verification before closing.
[16:15] <ogasawara> Bug 624915 - debian-installer issue which cjwatson has already resolved.
[16:15] <ogasawara> Bug 291760 - Numerous comments to the bug indicate this is not a kernel issue nor is there any confirmation against a Maverick kernel.  I've subsequently closed this bug against the kernel and posted a comment.
[16:15] <ogasawara> Bug 615400 - Believed to be resolved with the current kernel.  Waiting for verification before closing.
[16:15] <ogasawara> Bug 613855 - Patches applied and kernel uploaded (linux-2.6.35-19.26).
[16:15] <ogasawara> As a general status, we've rebased to the latest 2.6.35.3 upstream stable kernel which was basically a set of regression fixes from 2.6.35.2.  We also uploaded a kernel yesterday with fixes for 613855.  We are above the trend line for our Beta release burndown chart but below the trend line overall.  The remaining Beta release work items are not release critical.
[16:16] <ogasawara> Questions?
[16:16] <skaet> thanks ogasawara. :)
[16:16] <skaet> [TOPIC] Foundations team
[16:16] <MootBot> New Topic:  Foundations team
[16:17] <cjwatson> hi
[16:17] <cjwatson> https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Maverick#RC%20Milestoned%20bugs
[16:17] <cjwatson> hm
[16:18] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Maverick#RC%20Milestoned%20bugs
[16:18] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Maverick#RC%20Milestoned%20bugs
[16:18] <cjwatson> skipping the feature section there this week, as we should mostly be focusing on bugs now
[16:18] <cjwatson> two bugs I want to call out there
[16:19] <cjwatson> bug 613008: Evan says he can work on this on Tuesday, but will that be too late for beta?  if so, I can try to figure something out this afternoon
[16:19] <skaet> robbiew,  thoughts?
[16:20] <cjwatson> bug 441941: this has been around since we switched to grub2 in 10.04.  The limited actual data (as opposed to VERY large number of comments) in the bug suggests that it may be simply because grub2's core.img is somewhat bigger than grub legacy's stage1.5, in which case there is a very limited amount that we can actually do about this.  I acknowledge it's a serious issue for those affected, but wonder how much use it is ...
[16:20] <cjwatson> ... to treat it as RC
[16:21] <cjwatson> also, I downgraded bug 459639 to Medium.  Anyone affected by this should comment
[16:22] <robbiew> skaet: cjwatson: seems 613008 has a workaround
[16:22] <cjwatson> yes, be online
[16:22] <robbiew> so if we can't get it into Beta
[16:22] <robbiew> we should at least release note it...again :/
[16:23] <skaet> ok
[16:23] <skaet> any questions for colin?
[16:24] <skaet> thanks colin.
[16:24] <skaet> s/colin/cjwatson/  sigh....
[16:24] <skaet> [TOPIC] server team
[16:24] <MootBot> New Topic:  server team
[16:25] <ttx> hi!
[16:25] <ttx> Server team status is up to date at https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus
[16:25] <skaet> hi!
[16:25] <ttx> About Maverick bugs, I spent some time recently reviewing all High and a few Medium -server bugs to fill the bucket again. Here you go:
[16:25] <ttx> Beta-milestoned bugs:
[16:25] <ttx> Bug 619843 - euca-get-console-output returns one single line (Daviey): should be in next eucalyptus upload
[16:25] <ttx> Bug 599342 - Temporary failure in name resolution (hallyn): waiting for input from OP, potentially deferred
[16:25] <ttx> Bug 613535 - cloud-debug.log reports errno=2 trying to execute 'bttrack' (Daviey): should be in next eucalyptus upload
[16:26] <ttx> Bug 617053 - on upgrade from 1.6.2, euca_upgrade should preserve DISABLE_ISCSI="Y" (Daviey): needs verification, might be already fixed
[16:26] <ttx> High, release targeted bugs:
[16:26] <ttx> Bug 574665 - kvm + virtio disk corrupts >1TB large volumes (hallyn): more investigation required
[16:26] <ttx> Bug 564355 - run-instance request in same security group causes eucalyptus to remove network (hggdh): needs verification
[16:26] <ttx> Bug 584048 - kvm images losing connectivity w/bridged network (hallyn): nearing a solution
[16:26] <ttx> Bug 620441 - MySQL upstart stop job does not cleanly shutdown mysql (SpamapS): more investigation needed
[16:26] <ttx> Bug 606715 - Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid (ttx): triaged
[16:26] <ttx> Bug 619712 - keepalived vrrp race condition (RoakSoaX): patch needs verification
[16:27] <ttx> Then there is a list that I will spare you, maverick-targeted bugs that are more targets of opportunity for the next weeks
[16:27] <ttx> (medium or below)
[16:27] <skaet> :)
[16:27] <ttx> On the specs side...
[16:27] <ttx> Hm, wait
[16:27] <ttx> Maverick bugs affecting server, in other teams:
[16:27] <ttx> Bug 563916 - [details.so] No prompt for [S]kip or [M]anual recovery on server boot
[16:27] <ttx> This one is targeted to 10.04.2 as well
[16:28] <ttx> would be nice to fix in Maverick, but I suspect it's getting late
[16:28] <skaet> ttx,  what's the outlook for the fix?
[16:28] <ttx> it's in the hands of the Foundations team, I think Colin spent one of his remaining cycle on it
[16:29] <ttx> cjwatson: ^
[16:29]  * ttx will talk specs in the mean time.
[16:30] <ttx> Progress for the beta subcycle is at http://people.canonical.com/~pitti/workitems/maverick/canonical-server-ubuntu-10.10-beta.html
[16:30] <ttx> Beta-milestoned specs status:
[16:30] <ttx> server-maverick-upstart-conversion (0%): not completed in time for BetaFreeze. Underlying bug being fixed, those can be postponed to Natty.
[16:30] <ttx> server-maverick-uec-testing (40%): Most work items for beta testing week, should be completed in time
[16:30] <ttx> server-maverick-daily-vcs (50%): One work item left, on track (can be completed during freeze)
[16:30] <ttx> server-maverick-workitemtracker (64%): On track (can be completed during freeze)
[16:31] <ttx> server-maverick-community (67%): One work item left (assigned to jcastro)
[16:31] <ttx> server-maverick-papercuts (67%): One retrospective work item left, on track (can be completed during freeze)
[16:31] <ttx> server-maverick-uds-cloud-loadbalancing (75%): One work item left, on track (can be completed during freeze)
[16:31] <ttx> server-maverick-puppet-bootstrap (83%): One work item left, on track (can be completed during freeze)
[16:31] <cjwatson> skaet: current status is that it's awaiting feedback from the patch submitter on a question from upstream
[16:31] <ttx> server-maverick-cloud-images-sans-cloud (88%): One optional work item left, on track (can be completed during freeze)
[16:31] <ttx> The others are complete.
[16:31] <cjwatson> I'll move it forward if I have to, but was hoping to let the patch submitter do that since that's more economical of our resources
[16:31] <skaet> cjwatson,  thanks.
[16:31] <ttx> Other specs status:
[16:32] <ttx> server-maverick-hadoop-pig (0%): 3 work items (2 in progress), can all be completed during freeze
[16:32] <ttx> server-maverick-isotesting (0%): On track (work starts next week!)
[16:32] <ttx> server-maverick-uec-eucalyptus-next (58%): Will require another eucalyptus upload (BetaFreezeException)
[16:32] <ttx> skaet: ^
[16:32] <ttx> server-maverick-dailytriage (63%): On track (just a tracking spec)
[16:32] <ttx> server-maverick-uds-seed-review (93%): One work item left, on track (can be completed during freeze)
[16:32] <skaet> ttx,  ack.  will talk to robbiew
[16:33] <ttx> skaet: let's say that freezeexceptions for eucalyptus have been quite common in the past :)
[16:33] <ttx> Looking at it from a spillover/postponed perspective:
[16:33] <ttx> The server-maverick-qa-workflow spec was postponed due to work on eucalyptus blocking the QA resource
[16:33] <ttx> Some work items were postponed in server-maverick-community, server-maverick-uec-liveusb and server-maverick-hypervisor
[16:33] <skaet> heh.   Thanks for the context.  ;)
[16:33] <ttx> Some work items in server-maverick-uds-seed-review were remilestoned to maverick release
[16:33] <ttx> All work items in server-maverick-uec-liveusb were remilestoned to maverick release
[16:33] <ttx> That's all, thanks for your patience.
[16:33] <ttx> Questions ?
[16:34] <skaet> will upstart-conversion make it for release?
[16:35] <ScottK> upstart-conversion is a process, not a destination I feel.
[16:35] <ttx> no, I think it should be postponed to natty. It's work in progress anyway
[16:35] <ttx> yes.
[16:35] <skaet> cool.
[16:35] <ttx> so those specific scripts were nominated because...
[16:35] <ttx> there was some issue making lo unavailable in time for some legacy init scripts to behave properly
[16:35] <ttx> that issue was fixed, so it's "less pressing"
[16:36] <skaet> thanks.  makes sense.
[16:36] <ttx> and at that point, adding them is more a nuisance
[16:36] <ttx> given how close we are to release, and how critical an upstart script can be
[16:36] <ttx> I'm just waiting for jiboumans to be back to confirm the punting.
[16:37] <skaet> thanks ttx.  :)
[16:37]  * ttx bows.
[16:37] <skaet> lol
[16:37] <skaet> [TOPIC] Desktop team
[16:37] <MootBot> New Topic:  Desktop team
[16:37] <seb128> hi
[16:37] <seb128> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:37] <seb128> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team.html
[16:37] <seb128> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-ubuntu-10.10-beta.html
[16:37] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:37] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team.html
[16:38] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-ubuntu-10.10-beta.html
[16:38] <seb128> Work items summary:
[16:38] <seb128> We are on track for beta and maverick
[16:38] <seb128> Week work summary:
[16:38] <seb128>  * quite some bug fixing done
[16:38] <seb128>  * unity and dx weekly updates went it
[16:38] <seb128>  * chrisccoulson spent time on getting the "sending crashes directly to upstream" working and on getting the firefox4 builds going
[16:38] <seb128>  * xorg got some updates still
[16:38] <seb128>  * kenvandine sorted with twitter how we can get gwibber to work with the coming authentification changes
[16:38] <seb128>  * lot of ui tweaking rush and updates just before the ui freeze start
[16:38] <seb128>  
[16:38] <seb128> Questions for beta:
[16:38] <seb128>  * the GNOME 2.32 beta tarballs are due on monday, can we get those uploaded for beta or not?
[16:38] <seb128>  * firefox 3.6.9 is ready for upload with the fix for sending crashes directly to upstream, not langpacks change required, can we upload today or should that go after beta?
[16:38] <seb128>  * banshee by default on UNE is really late, the version using udev will have it first tarball next week and it has new depends (one being in universe, one not packaged yet), is there a way we can still do that change for maverick after beta (it's UNE only)?
[16:38] <seb128>  
[16:38] <seb128> (I will give the remaining summary and bugs once those are sorted)
[16:39] <skaet> robbiew,  cjwatson,   thoughts?
[16:39] <seb128> I guess for GNOME we can do the "just upload and people will review and decide"
[16:40] <skaet> heh,  true...
[16:40] <seb128> if those go after beta that's ok
[16:40] <robbiew> the firefox upload should go in pre-beta
[16:40] <robbiew> I think
[16:40] <seb128> I would like to get firefox 3.6.9 in though, that would give us testing and make the crash reports work with upstream which is a real win
[16:40] <robbiew> +1
[16:40] <seb128> ok, great
[16:41] <seb128> skaet, no objection?
[16:41] <skaet> +1
[16:41] <seb128> thanks
[16:41] <seb128> I guess we can sort the banshee one next week when didrocks (our UNE maintainer) is back
[16:41]  * skaet thinks more testing with beta the better.....  
[16:41] <seb128> it's not really blocking beta
[16:41] <seb128> I just wanted to mention it
[16:41] <robbiew> seb128: agree on waiting on banshee decision
[16:42] <seb128> ok
[16:42] <seb128> should I continue with the remaining bits?
[16:42] <skaet> [ACTION] discuss with didrocks banshee on UNE
[16:42] <MootBot> ACTION received:  discuss with didrocks banshee on UNE
[16:42] <skaet> seb128, yes please.
[16:42] <seb128> one comment
[16:42] <seb128> Worth noting that software-center still use a ppa rather than extras.ubuntu.com which is blocked on being set up by I.S, changing the archive to use should not be an issue but might be worth knowing
[16:42] <seb128>  
[16:42] <seb128> not sure if that's an issue or not or if foundation, mvo are tracking that
[16:43] <seb128> I though I would mention it since we have remaining beta work items for those
[16:43] <seb128>  
[16:43] <seb128> other bugs from the agenda:
[16:43] <seb128> * bug 16492: changed to low, that's basically a wishlist and not a maverick milestoned issue (was changed last week, why is it still listed? do you disagree with the change?)
[16:43] <seb128> * bug 329898: bug assigned to our printing maintainer and under investigation, could be due to ibus
[16:43] <seb128> * bug 522538: bug assigned to the gwibber maintainer for investigation
[16:43] <seb128> * bug 575160: universe bug assigned to a community member, is there any reason it's on the desktop team list?
[16:43] <seb128> * bug 602899: bug assigned to our xorg maintainer who thinks it might be fixed in the current version, needs confirmation from the submitter
[16:43] <seb128> * bug 603507: not really a blocker since it's not an issue for unity out of the debug mode and there is a workaround, I've set it to low
[16:43] <seb128> * bug 610600: the issue is being investigated and discussed with upstream, it's better in maverick but we don't really have the competence in the team to work on it directly
[16:43] <seb128> * bug 615549: needs input from Keybuk or somebody who knows about upstart
[16:43] <seb128> * bug 616023: nvidia binary driver issues, jockey workaround it for now and we will get the update case fixed for maverick as well
[16:43] <seb128> * bug 621433: is being worked by the ubuntuone team
[16:43] <seb128> * bug 623509: the fix is ready to uploaded with firefox 3.6.9, cf question before
[16:43] <seb128> bug fixed on the week list: bug #623655
[16:43] <seb128> bugs from the previous week fixed this week: #595555 #606728 #616515 #618945 #619858
[16:44] <seb128>  
[16:44] <seb128> that's it
[16:44] <seb128> I'm open to questions or comments ;-)
[16:44] <skaet> [ACTION] skaet follow up onsoftware-center using ppa rather than extras.ubuntu.com
[16:44] <MootBot> ACTION received:  skaet follow up onsoftware-center using ppa rather than extras.ubuntu.com
[16:44] <cjwatson> sorry, was writing an extremely long follow-up to 441941 ...
[16:44] <seb128> not sure what format you prefer for the bugs listed on the agenda
[16:44] <cjwatson> Monday might be OK, I imagine Tuesday's ISOs will be the candidates we work on?
[16:44] <seb128> the IRC dump doesn't seem really digest
[16:45] <seb128> we have a summary on our weekly wiki summary
[16:45] <davidbarth> seb128: you put the bot on his knees
[16:45] <seb128> davidbarth, blame whoever put the agenda list and assign all those bugs to us :p
[16:46] <skaet> seb128,  heh...  can you look at 522538 as well
[16:47] <seb128> bug #522538
[16:47] <seb128> skaet, it was the third one in my copied list
[16:47] <seb128> but I didn't put it on the wiki yet because it has been added during the day
[16:47] <seb128> will do that now
[16:47] <skaet> seb128 - ack missed it in the scan.... :(
[16:48] <seb128> let me know if another format would work better
[16:48] <seb128> I'm not sure triggering the bot for having the url and bug title is useful or noise
[16:49] <skaet> seb128,  thanks.    :)    will keep with current format for now
[16:49] <seb128> skaet, ok
[16:49]  * skaet still figuring things out...
[16:49] <seb128> you're welcome
[16:49] <skaet> [TOPIC] kubuntu
[16:49] <MootBot> New Topic:  kubuntu
[16:49] <ScottK> Riddell is offline today, so I'll cover Kubuntu.
[16:49] <skaet> thanks
[16:49] <ScottK> [LINK] http://tinyurl.com/33p7vu3 - Not a lot in the way of milestoned bugs:
[16:49] <ScottK> [LINK] https://wiki.kubuntu.org/Kubuntu/Todo - Spec status is (newly updated). We may have some FFe yet if some tasks get finished, but it won't be anything potentially disruptive.
[16:49] <ScottK> Ubiquity KDE overaul landed yesterday.  Don't have any test reports yet.
[16:49] <ScottK> After beta is out we'll be updating KDE to 4.5.1 and qt4-x11 to 4.7.0 rc1 (we have the beta now).
[16:49] <ScottK> Build issues on armel are finally resolved, so we should have images for beta.
[16:49] <MootBot> LINK received:  http://tinyurl.com/33p7vu3 - Not a lot in the way of milestoned bugs:
[16:49] <MootBot> LINK received:  https://wiki.kubuntu.org/Kubuntu/Todo - Spec status is (newly updated). We may have some FFe yet if some tasks get finished, but it won't be anything potentially disruptive.
[16:50] <ScottK> First test images for kubuntu-mobile tech preview (Universe) rolled yesterday, should have them in production soon.
[16:50] <ScottK> Questions?
[16:50] <ScottK> The biggest uncertainy for beta is the installer.
[16:51] <skaet> ScottK  images for mobile looked a bit big for ISO.   who's going to do pruning?
[16:51] <ScottK> skaet: I'm planning on bumping the size limit.  These aren't really aimed at CD, but install via USB, so size isn't a concern.
[16:52] <ScottK> (we did this for Kubuntu Netbook when it was a separate image)
[16:52] <skaet> ScottK,  cool.  Thanks for explanation.  :)
[16:52] <ScottK> That said, it could stand some pruning as it has too much standard desktop stuff that's not needed.
[16:52] <skaet> heh
[16:53] <skaet> ScottK,  thanks!
[16:53] <skaet> [TOPIC] Desktop experience
[16:53] <MootBot> New Topic:  Desktop experience
[16:53] <skaet> hmm... anyone around, or is this still a gap?
[16:54] <ScottK> Should be davidbarth
[16:54] <iainfarrell> dbarth and i are here
[16:54] <davidbarth> oops
[16:54] <davidbarth> yes
[16:54] <ogra> talk to us then, dont be shy :)
[16:54] <skaet> cool.   updates?
[16:54] <davidbarth> sure
[16:54] <davidbarth> https://wiki.ubuntu.com/DesktopExperienceTeam/MaverickReleaseStatus
[16:54] <davidbarth> contains the summary
[16:55] <davidbarth> in summary, we have 1 small missing for appmenu
[16:56] <davidbarth> a series of UIF exceptions for indicators
[16:56] <davidbarth> 1 UIF exception for unity also (couldn't get all of the artwork on time)
[16:57] <davidbarth> and (yet) another exception request for the MT integration in unity
[16:57] <davidbarth> i don't want to sound like we haven't worked during the past weeks though
[16:58] <skaet> davidbarth,  any thoughts on bug #606052?
[16:58] <davidbarth> in particular, more than 40 bugs / tasks were closed for unity in the last 4 days (https://bugs.launchpad.net/unity/+milestone/2010-08-26)
[16:58]  * skaet likes hearing about bugs being closed.   :D
[16:59] <davidbarth> none sorry, was not on my radar
[16:59] <davidbarth> but will now
[16:59] <skaet> davidbarth,  thanks!
[16:59] <ScottK> davidbarth: Is the Ubuntu font your issue or Ux?
[17:00] <davidbarth> i've browsed other critical bugs today, but can you send me the release meeting invite to be able to give you a more accurate report on bugs next week?
[17:00] <davidbarth> font is ux
[17:00]  * ScottK waits.
[17:00] <davidbarth> iainfarrell is present today for design
[17:01] <iainfarrell> We raised the issue of the font with Mark on the DX call this week
[17:01] <skaet> [ACTION] skaet to review release meeting invite list and make sure davidbarth is on it.
[17:01] <MootBot> ACTION received:  skaet to review release meeting invite list and make sure davidbarth is on it.
[17:01] <iainfarrell> he's not satisfied that we're ready to add this to the distro yet
[17:01] <davidbarth> skaet: thanks ;)
[17:01] <davidbarth> questoins for DX?
[17:01] <iainfarrell> We are attetmpting to answer his concerns
[17:01] <iainfarrell> I can't provide a deadline unfortunately
[17:01] <iainfarrell> Ivanka has been meeting and reviewing with him
[17:01] <davidbarth> ie, i've discussed that status with seb128 this mornng to plan for the reviews necessary for landing fixes
[17:01] <ScottK> iainfarrell: So it's still a potential FFe request for Maverick then.
[17:02] <iainfarrell> ScottK: correct
[17:02] <iainfarrell> worse is that I was expecting an update on conversations but their internet connection has died
[17:02] <iainfarrell> so I won't get an update now until Tuesday at the earliest
[17:03] <iainfarrell> Should I add this detail as a comment to the font bug?
[17:03]  * ScottK would think so.
[17:03] <iainfarrell> ScottK will do
[17:04] <skaet> ianfarrell, davidbarth,   thanks!
[17:04] <skaet> [TOPIC] user experience
[17:04] <MootBot> New Topic:  user experience
[17:05]  * skaet looks around... 
[17:05] <davidbarth> iainfarrell: that's you again dude ;)
[17:06] <davidbarth> skaet: iainfarrell didn't get the invitation email either i guess
[17:06] <davidbarth> but looking at the blueprints that were listed in a previous email
[17:06] <skaet> [ACTION] skaet to make sure iainfarrel is on the invite too...
[17:06] <MootBot> ACTION received:  skaet to make sure iainfarrel is on the invite too...
[17:07] <iainfarrell> Thanks skaet
[17:07] <davidbarth> the generative wallpaper one had to be postponed unfotrunately (DX could allocate ressources to work on that)
[17:07] <davidbarth> the theme enhancements are mostly complete i guess
[17:08] <davidbarth> and the papercuts are, well... bugs, so the high/critical ones are still in scope for the beta iteration i assume
[17:08] <iainfarrell> davidbarth: That's correct we're just testing and will only ask to make changes for bug fixes at this stage
[17:08] <iainfarrell> yes, and we're over 100 papercuts too - thanks to vish
[17:08] <iainfarrell> who's not here but if you see him send our love :)
[17:08] <skaet> :)
[17:08]  * vish here o/
[17:09] <skaet> any questions?
[17:09] <skaet> [TOPIC] ARM team
[17:09] <MootBot> New Topic:  ARM team
[17:09] <ogra> hohoho, thats me !
[17:09] <ogra> Detailed status at: https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Maverick
[17:09] <ogra> ...
[17:09] <ogra> Short summary:
[17:09] <ogra>  * oem-config issues with the current images (Bug #616581) were fixed with the most recent ubiquity upload
[17:09] <ogra>  * ubuntu-netbook-efl-default-settings is still pending fixes to the default 2D session for which we will need freeze exceptions (this package only shows up on the armel images)
[17:10] <ogra>  * ongoing "normal" work on main ftbfs, most packages from main are off the list, the blocking telepathy-glib FTBFS was worked around by dropping optimization for now
[17:10] <ogra>  * a massive issue with networking that tears down the whole board has been worked around (the new silicon we're about to get will fix that see bug 625108)
[17:10] <ogra>  * dove images are building daily now
[17:10] <ogra>  * kubuntu armel images are building daily now
[17:10] <ogra> ...
[17:10] <ogra> Beta status (somehow the tracker didnt update, that should look different):
[17:10] <ogra> http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[17:10] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10-beta.html
[17:10] <ogra> ...
[17:10] <ogra> Beta targeted specs:
[17:10] <ogra> none anymore, all postponed until after beta or ready to drop
[17:10] <ogra> ...
[17:10] <ogra> Bugs:
[17:10] <ogra> 5 went into fix committed/released status
[17:10] <ogra> ...
[17:10] <ogra> 7 still open for post beta work
[17:10] <ogra> ...
[17:10] <ogra> 2 Release blockers
[17:10] <ogra> ...
[17:10] <ogra> 2 bugs that will need beta freeze exceptions
[17:10] <ogra> bug 613606
[17:10] <ogra> bug 613230
[17:10] <ogra> err
[17:10] <ogra> the latter one isnt quite right
[17:11] <ogra> ah, not its just the order the bot throws them out
[17:12] <skaet> ogra, any update on bug#615773?
[17:12] <ogra> bug 615773
[17:13] <ogra> skaet, no and that has to happen post beta
[17:13] <skaet> ack.
[17:13] <ogra> the current HW we support doesnt use eMMC, we're getiing there soon :)
[17:13] <skaet> good reason;)
[17:13] <ogra> whole team just gets HW upgardes with new silicon
[17:14] <ogra> yeah, working with pre-production HW is *lots* of fun :)
[17:14] <skaet> lol
[17:14] <skaet> any questions?
[17:14] <ogra> especially if you also have pre-rpoduction kernels :)
[17:15]  * skaet snickers... indeed.
[17:15] <skaet> thanks ogra.
[17:15] <ogra> :)
[17:15] <skaet> [TOPIC] MOTU
[17:15] <MootBot> New Topic:  MOTU
[17:15]  * ScottK waves
[17:15] <skaet> :)
[17:16] <ScottK> lucas is going to do another archive rebuild early next week so we should have a current FTBFS list soon.
[17:16] <ScottK> Lots of NBS work and FTBFS left.  Since we've dropped sparc and ia64 it's hard to say exactly how we compare to previous releases.
[17:17] <ScottK> Nothing more to report.
[17:17] <skaet> ScottK, any update on bug 615773 ?
[17:17] <ogra> go ScottK, fix it ! :)
[17:17]  * skaet smiles - she got the syntax right for the bot ... finally
[17:17] <ScottK> No.
[17:18] <skaet> s/me hangs head.... typo.  arrgh.
[17:18] <skaet> bug 610975
[17:18] <ogra> gah i was hoping you tell him to fix it for us :)
[17:19] <ScottK> No.  I need to understand where we are on that.
[17:19] <ScottK> Not just for maverick but due to the SRU regression.
[17:19] <skaet> hmm.... that bug is not matching the notes in agenda....   will clean up...
[17:20] <skaet> bug in agenda was saying can not start pgadmin3...  cut and paste issue I guess..
[17:20] <ScottK> wx is typically a pile of pain in any case.
[17:20] <ScottK> It's the same bug.
[17:21]  * skaet learns....
[17:21] <skaet> ScottK thanks
[17:21] <skaet> [TOPIC]  Linaro
[17:21] <MootBot> New Topic:   Linaro
[17:22] <JamieBennett> Nothing much release wise for Linaro, we are on top of the existing 3 bugs and there may be a FFe request for a new kernel update before beta but that's all to report. Things are good in Linaro land ATM.
[17:22] <skaet> cool.
[17:22] <ScottK> Is the linaro kernel used on any ISO's built by Ubuntu?
[17:22] <ogra> no, only their bootloader will be soon
[17:23] <ScottK> OK.  Thanks.
[17:23]  * JamieBennett nods
[17:23] <ogra> we might switch in natty for omap
[17:23] <skaet> any other questions?
[17:24] <skaet> [TOPIC] 10.4.2 LTS
[17:24] <MootBot> New Topic:  10.4.2 LTS
[17:24] <ScottK> FYI, u-boot-linaro is in binary New, so you should bribe some archive admin to push it out.
[17:24] <ogra> ScottK, jdstrand is on it
[17:25] <skaet> any other things to talk about before closing the meeting?
[17:26] <ogra> skaet, you did very well for your first time, kudos
[17:26] <jdstrand> ogra: accepted
[17:26] <ScottK> When do we plan to start rolling "final" images for beta?
[17:26] <skaet> cjwatson: ^
[17:26] <cjwatson> I was thinking first thing Tuesday?
[17:26] <ScottK> Sounds good.
[17:26] <cjwatson> if that works for people
[17:26] <cjwatson> if nothing else, Monday's a bank holiday here
[17:27]  * ogra hugs jdstrand 
[17:27] <JamieBennett> Yeah, day off ftw ;)
[17:27] <jdstrand> :)
[17:28]  * skaet notes not to call folks on monday.
[17:28] <skaet> thanks all.
[17:28] <skaet> #endmeeting
[17:28] <MootBot> Meeting finished at 11:28.
[17:30] <seb128> thanks skaet
[17:30]  * skaet toddles off to start grubbing through bugs some more....
[17:30] <skaet> seb128, obra,  thanks.
[17:31] <seb128> skaet, btw be aware that retracers are still down
[17:31]  * ScottK hands skaet a 'g'.
[17:31] <seb128> so we get no crash bugs going through
[17:31] <seb128> launchpad guys said they would have a workaround in early next week
[17:31] <skaet> seb128,  retracers?  education please.... new term.
[17:31] <seb128> skaet, do you know about apport?
[17:32] <seb128> not sure where to start the explanations ;-)
[17:32] <seb128> skaet, it's our bug reporting software, it catches crashes
[17:32] <skaet> seb128,  heh,  heard the terms,  will start grilling robbiew
[17:32] <seb128> skaet, you can apt-cache show apport
[17:33] <skaet> cool.
[17:33] <robbiew> skaet: or talk to the guy who wrote apport
[17:33] <seb128> skaet, basically when something crashes apport get the coredump of the crash
[17:33] <robbiew> heh
[17:33] <seb128> skaet, add some extra informations on your system, package versions, etc
[17:33] <seb128> collect some infos specific to the package
[17:33] <seb128> and send that to launchpad
[17:34] <seb128> crash bugs are private by default
[17:34] <seb128> often the users don't have debug symbols
[17:34] <seb128> so we have services in the dc running and going through those bugs
[17:34] <seb128> using apport-retrace
[17:34] <seb128> which is basically a "get the summary of the package installed and its depends, install the corresponding -dbgsym in a sandbox, use gdb on the coredump, get a debug stacktrace"
[17:35] <seb128> those go through crashes bugs on launchpad, get the stracktrace, clean the coredump and subscribe bugsquad
[17:35] <skaet> can understand, very useful on getting meaningful info from the bug when the user may not know what to send.
[17:35] <seb128> the bugsquad from there can review the stacktrace for private info and mark those public
[17:36] <seb128> that's the theory
[17:36] <skaet> because certain customers may have confidential data in the trace?
[17:36] <seb128> right now bug #620458 breaks this service
[17:36] <seb128> so the service doesn't run
[17:36] <skaet> why is it considered Low then?
[17:36] <seb128> the crashes are not processed, the triagers not subscribed
[17:37] <seb128> so we pile bugs nobody has access to
[17:37] <seb128> skaet, triaging error, they have made it a high priority and are working actively on it since it's known
[17:37] <seb128> it's handled as a high priority bug
[17:37] <seb128> the status is wrong there
[17:37] <skaet> whew...
[17:37] <seb128> skaet, <skaet> because certain customers may have confidential data in the trace?
[17:37] <seb128> not only customer
[17:38] <seb128> rather any user
[17:38] <seb128> if your email client crash the coredump might have your password in clear in the coredump
[17:38] <seb128> or the content of the email you were reading
[17:38] <seb128> we can let access to the coredump due to that
[17:39] <seb128> well the summary is that none of the crash bugs are reaching us
[17:39] <skaet> makes sense.
[17:39] <seb128> there a backlog of some hundred bugs to retrace
[17:40] <skaet> hmm,  will talk this over a bit with marjo, and see what can be done.
[17:40] <seb128> skaet, not sure if you have a metric for bugs yet but common crashes collect quite some duplicate counts
[17:40] <marjo> skaet: ack
[17:40] <seb128> I saw you called a dx indicator crash without duplicate before
[17:40] <skaet> thanks for making me aware of it, and giving me the context to understand.  :)
[17:40] <seb128> not sure if you picked just that one, but don't pay lot of attention with crashes without debug stacktrace or duplicates
[17:40] <seb128> they are often not worth it
[17:41] <ScottK> Although, as seb128 says, the Launchpad team have prioritized this appropriately, it is not unheard of for the LP priority not to match the importance Ubuntu developers feel an LP bug should have.
[17:41] <seb128> real issue collect ten of duplicates every week usually
[17:41] <skaet> seb128, heh, gotcha.
[17:41] <seb128> skaet, oh, another detail, the retracers have auto duplication
[17:41] <marjo> seb128: that's one of the many challenges: too many duplicates
[17:41] <seb128> skaet, they have a database of crash signature and auto close as duplicate the ones matching a known signature
[17:42] <seb128> marjo, the retracers deal just fine with those usually
[17:42] <marjo> seb128: ack
[17:42] <seb128> marjo, that should not be visible to anybody, they don't send email and just autoclose them as duplicate
[17:43] <seb128> skaet, not sure I've been really clear, there is documentation about apport on the ubuntu wiki
[17:43] <seb128> skaet, you can also ask questions if some details are not clear
[17:44] <ScottK> Short version of the docs is "ask pitti, he knows all about it."
[17:44] <skaet> seb128, thanks!   will hunt down those wiki pages.
[17:44] <skaet> ScottK,  lol.  :)  thanks.
[17:47]  * skaet adds some wiki hunting, to the bug grubbing, and poking around with apport to the afternoon list