User1: is it o/ ? or in 1h ?
User2: in 1h, slangasek said 1600 UTC
User1: kk
User1: time to take a break then ;)
User3: yep - sorry, forgot that Google Calendars don't understand UTC
User4: heh ...
User4: they are useless inseed
User5: someone fix that to topic? helps avoid some confusion
User6: User5 You mean add "Google Calendar doesn't understand UTC : please reschedule any meetings that are wrong"?
User5: User6 yeah.  something to that end
User5: User6 or Google Calender doesn't understand UTC.  Please check in UTC time and confirm meeting time"
User6: User7 If you have a moment? ^^
User7: who what when?
User6: If you could add a hint in the topic that Google Calendar is a little confused about UTC, and people should confirm their meeting times, it may lead to more sanity.
User5: Refer to UTC time in http://fridge.ubuntu.com/calendar
* jussi01 changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Google Calender doesn't understand UTC.  Please check in UTC time and confirm meeting times on the fridge
User7: hows that?
User5: User7 thats great :)
User5: I've seen a bunch of people confused this week :)
User6: User7 Thank you very much.
 * pitti waves
 * marjo waves
User8: oh aye, I need to update the Kubuntu status
 * apw looks nonchalant
 * slangasek waves
User9: so, slangasek is still 150% involved in pushing out the beta
User9: so let's start
User9: #startmeeting
User10: Meeting started at 11:02. The chair is pitti.
User10: Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
User2: o/
User9: first, thanks to everyone helping out with release, bug fixing, testing, etc!
User9: [TOPIC] Actions from previous meetings
User10: New Topic:  Actions from previous meetings
User3: [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-19
User10: LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-19
User1: o/
User9: review status of branding for Kubuntu, Edubuntu next week
User9: stgraber, Riddell ?
User8: we got a bit further with designs from the design team, and some from Kubuntu people
User8: still waiting on that crucial "k" letter
User1: didnt get an answer on my mozilla cairo ping last friday. failed to send mail as i was gone more than half of the week - will draft that now
User1: (for my action)
User9: User1 thanks, rolling over then
User3: User8 how far is "a bit further"?
User9: [ACTION] asac to talk to mozilla upstream about the need for system cairo in Ubuntu
User10: ACTION received:  asac to talk to mozilla upstream about the need for system cairo in Ubuntu
User1: ack
User3: User8 and more importantly, does everyone know in whose court the ball is right now?
User9: User8 is there something code/packging wise still missing aside from the artwork itself?
User9: User8 i. e. is it just updating graphics, or do we need new packages, especially wrt. plymouth etc.?
User8: User3 they sent us some designs which aren't yet finished, we're still picking from the design choices.  so ball in both courts
User3: User8 ok
User8: User9 new plymouth package I believe, some file changed in kubuntu-default-settings
User9: ok, thanks
User9: carrying over then
User9: [ACTION] review status of branding for Kubuntu, Edubuntu next week
User10: ACTION received:  review status of branding for Kubuntu, Edubuntu next week
User9: ScottK, slangasek to review python sync/merge candidates ~Mar 12
User3: User9 not done yet, carry over
User9: [ACTION] ScottK, slangasek to review python sync/merge candidates
User10: ACTION received:  ScottK, slangasek to review python sync/merge candidates
User11: slangasek types faster than I do ...
User9: [TOPIC] QA team
User10: New Topic:  QA team
User9: User12 floor is your's
User9: how bad is it? :-)
User12: User9 let's do the good news first
User12: * Hardware testing
User12: http://people.canonical.com/~fader/hw-testing/current.html
User12: Netbook:
User12: passed:  13 (100%)   failed:   0 (  0%)   untested: 0 (  0%)
User12: Laptop:
User12: passed:  32 (97%)   failed:   0 ( 0%)  untested: 1 ( 3%)
User10: LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
User12: Server:
User12: passed:  61 (90%)   failed:   0 ( 0%)  untested: 7 (10%)
User12: Desktop:
User12: passed:  13 (100%)   failed:   0 (  0%)   untested: 0 (  0%)
User12: User9 nice huh?
User9: sweet!
User9: 0 failures?
User9: I hope it's not a failure of the tests :)
User12: the untested systems are being brought up
User2: User9 we finally fixed all the bugs !
User13: that's way better than I was expecting, given my bug mailbox
User9: let's go have beer
User9: I wonder why we have 90 pending uploads in unapproved then, and 130 RC bugs :)
User12: User9 please hold
User14: These are the automated tests, remember :)  We've got another round of manual tests planned to run on the beta
User9: User12 j/k
User12: fader_ is mr. realistic
User12: * Beta 1 Interim Test Report
User12: Lucid Beta 1 Interim Test Report
User12: 2010-03-19 0920 ET = 1320 UTC
User12: == Test Coverage ==
User12: ISO image = 100%
User12: === Untested test cases ===
User12: All mandatory test cases covered.
User12: Note: kubuntu i386 wubi install is currently broken (per davmor2 & slangasek)
User12: Interim, since final test failure analysis is in progress
User12: == Serious Bugs Status ==
User12: Sorted by status from New to Fix Released
User12: #541829 | Kde wubi crashes on r174
User12: ubiquity (Ubuntu)                      | Undecided | New
User12: ubiquity (Ubuntu Lucid)                | Undecided | New
User12: #541029 | netboot image fails to connect to the network
User12: linux-fsl-imx51 (Ubuntu)               | Undecided | New
User12: #541399 | netboot image fails to boot.
User12: linux-mvl-dove (Ubuntu)                | Undecided | New
User12: #541452 | ltsp on ubuntu is crashing with a sync issue stopping the kernel from booting
User12: ltsp (Ubuntu)                          | Undecided | New
User12: #539710 | OEM Lucid installation - configuring system for a new user - error occurring installing new packages
User12: ubiquity (Ubuntu)                      | High      | New
User12: #275998 | internal mic capture very low volume when routed through pulseaudio
User12: Dell Ubuntu Project                    | Undecided | In Progress
User12: Linux                                  | Undecided | Invalid
User12: PulseAudio                             | Unknown   | Unknown
User12: alsa-lib (Ubuntu)                      | Wishlist  | Triaged
User12: linux (Ubuntu)                         | Undecided | New
User12: pulseaudio (Ubuntu)                    | Undecided | Incomplete
User12: alsa-lib (Fedora)                      | Unknown   | Won't Fix
User12: pulseaudio (openSUSE)                  | Undecided | Invalid
User12: #539878 | nouveau out of sync LVDS (basically card not supported)
User12: linux (Ubuntu)                         | Undecided | New
User12: #539324 | Setting up swap fails when setting lvm+encryption
User12: debian-installer (Ubuntu)              | High      | Confirmed
User12: debian-installer (Ubuntu Lucid)        | High      | Confirmed
User12: #528678 | kubuntu Lucid ISO test alpha3 64 bits failed
User12: ubiquity (Ubuntu)                      | Undecided | Confirmed
User12: #409819 | [regression] Built-in mic not working after pulse updates on Karmic.  Intel 82801H (ICH8 Family) sound card.
User12: pulseaudio (Ubuntu)                    | Undecided | Confirmed
User12: #519541 | Abiword 2.8.1 freezes with document lost when help is clicked or F1 is pressed
User12: AbiWord                                | Unknown   | Confirmed
User12: abiword (Ubuntu)                       | High      | Triaged
User12: abiword (Ubuntu Lucid)                 | High      | Triaged
User12: #527401 | grub-installer fails to install on a raid1 array
User12: grub2 (Ubuntu)                         | High      | Triaged
User12: grub2 (Ubuntu Lucid)                   | High      | Triaged
User12: #540938 | oem-config-kde does not log out after setup
User12: ubiquity (Ubuntu)                      | High      | Fix Committed
User12: ubiquity (Ubuntu Lucid)                | High      | Fix Committed
User12: #540895 | Kubuntu OEM install does not install oem-config
User12: ubiquity (Ubuntu)                      | High      | Fix Committed
User12: ubiquity (Ubuntu Lucid)                | High      | Fix Committed
User12: #541607 | Lucid: Wubi drops immediately into grub shell on reboot
User12: Wubi                                   | Undecided | Fix Committed
User12: #540256 | enter kills X when booting Live CD or w/cryptsetup with plymouth text plugin
User12: plymouth (Ubuntu)                      | Critical  | Fix Released
User12: upstart (Ubuntu)                       | Critical  | Fix Released
User12: #541607 | Lucid: Wubi drops immediately into grub shell on reboot
User12: Wubi                                   | Undecided | Fix Committed
User12: #527623 | Notification of missing language support not shown after installation
User12: Ubuntu Translations                    | High      | Triaged
User12: language-selector (Ubuntu)             | High      | Fix Committed
User12: language-selector (Ubuntu Lucid)       | High      | Fix Committed
User12: #541625 | [lucid] Ubuntu Studio 64bit alternate DVD as of 18 March is missing kernel packages
User12: base-installer (Ubuntu)                | High      | Fix Committed
User12: #540878 | Xubuntu fails to localize the system into Spanish
User12: Ubuntu CD Images                       | Medium    | Fix Committed
User12: ubiquity (Ubuntu)                      | Medium    | Fix Committed
User12: #539507 | System Freeze/Pause waiting for something
User12: xorg (Ubuntu)                          | High      | Incomplete
User12: #541647 | Lucid-dvd-amd6.iso: installation via d-i shows Server selection
User12: debian-installer (Ubuntu)              | Critical  | Invalid
User1: hmm. wouldnt it be better to have this long report on a weekly release status page?
User12: User1 sure, it's usually not this long
User1: heh ok
User3: seems about standard length to me. :)
User1: its wiki format. is that on some wiki page we could paste instaed?
User3: it's not wiki format
User12: User1 i can do that in the future
User12: if that makes more sense on an IRC meeting
User12: User3 ready for specs status?
User1: dont do it just for me ... just thought i could better look at this on a wiki page ;)
User9: re (argh, X froze, sorry)
User12: User1 thanks for the feedback
User3: User12 I think so
User12: Specs Status
User12: http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
User12: * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
User12: All work items completed; beta available
User12: * UbuntuSpec:qa-lucid-improve-server-testcases
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
User12: Determine which test cases are required for the ISO tracker: DONE
User12: Write a new test case for a non internet connection install: DONE
User12: Write a new test case for a Kickseed install: DONE
User12: Write a new test case for a repair system install: INPROGRESS
User12: (Target completion date: Today, 2010-03-19)
User12: Bug:530380: checkbox writes to .cache/checkbox/submission before submission completes
User12: Status: Will submit merge request today
User3: User12 (another optimization would be to not list both 'ubuntu' and 'ubuntu lucid' tasks, they're always the same thing whenever they're relevant)
User12: User3 ack
User12: User3 that's all from QA team
User9: any questions for QA?
User9: User12 thanks
User9: [TOPIC] Server
User10: New Topic:  Server
User9: User2 hello
User12: I want to thank everyone who helped with ISO testing!
User2: User9 hi!
User2: https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
User9: User2 how did the beta-1 testing look server-wise?
User9: [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
User10: LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
User2: very-recently updated status ^
User2: User9 quite good
User2: The only big issues are those that affect more than server, like RAID1 / LVM+encryption
User9: I saw that one in many iso test cases indeed
User2: The rest was quite ok.
User2: Beta1 postmortem:
User9: is that on your team's radar? or do we need to find a home for it?
User2: User9 it's on Foundations radar already
User13: yes
User2: We had quite a few specs overflowing:
User2: server-lucid-uec-testing -- 15% spillover -- Test rig handover to QA and multi-network test automation not completed
User2: server-lucid-ec2-ebsroot -- 16% spillover -- Some release automation work still in progress
User2: server-lucid-apt-mirror-ec2 -- 33% spillover -- Blocked on IS delivery, only validation step remaining
User2: server-lucid-eucalyptus-merging-and-packaging -- 43% spillover -- Unable to solve upgrade issues in time for beta1, on site at Eucalyptus next week
User2: server-lucid-puppet-uec-ec2-integration -- 45% spillover -- Most of the investigation done, documentation left
User2: for that last one, % spillover does not really reflect how little work is left to be done.
User2: On the beta2 side, we have quite a few beta2 targets
User2: See the report for details on targeted bugs
User2: i'll do a pass next week to identify some potentially overlooked targets
User9: that bug list looks fairly reasonable for a three week period
User2: User9 yes, that's why I'll do a new pass on the bugs to try to find the hidden gem
User2: Bugs affecting server, in other teams:
User9: User2 do you think the remaining bits of the specs fit into the next three weeks, or will you have to drop some bits?
User9: 76 WIs seems quite much
User2: User9 all spillover has been retargeted to beta2, we might have to drop one spec: https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-id-mgmt-reference-env
User9: User2 that one is not even on http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-2.html
User2: Also please note that ~25 of those are linked testsuite bugs on server-lucid-puppet-uec-ec2-integration
User9: ah, ok
User9: User2 well, as long as you think that it's under control, that's fine :)
User2: which are not "necessary to fix" :)
User9: it seems quite a lot at first sight
User2: it's mathiaz's fault. He creates and links small bugs :P
User2: Bugs affecting server, in other teams:
User2: bug 531494: upstart does not run cloud-init job (Foundations)
User15: Launchpad bug 531494 in upstart "cloud-init job sometimes not running in cloud images without ramdisk" [Critical,Incomplete] https://launchpad.net/bugs/531494
User2: apparently there is a mismatch between what smoser provided and what keybuk is expecting, trying to solve it right now
User16: User9 it may seem a lot, but we're quite confident in our velocity. Also, we have some slack in the specs as ttx mentioned
User2: since we need an assignee on that one :)
User2: bug 527208: EC2 kernel fails to boot in c1.xlarge (Kernel)
User15: Launchpad bug 527208 in linux-ec2 "ec2 instance fails boot, no console output on c1.xlarge" [High,Confirmed] https://launchpad.net/bugs/527208
User2: jjohansen reported nice progress on this one
User2: bug 527401: grub-installer fails to install on a raid1 array (Foundations)
User15: Launchpad bug 527401 in grub2 "grub-installer fails to install on a raid1 array" [High,Triaged] https://launchpad.net/bugs/527401
User2: a well-known work in progress
User2: Other Lucid-targeted bugs:
User2: bug 520715: eglibc / puppet issue (Foundations)
User15: Launchpad bug 520715 in ruby-defaults "building ruby1.8 with pthread support causes puppet hangs" [Undecided,Triaged] https://launchpad.net/bugs/520715
User2: we might need to raise priority on this one if it's indeed as blocking as it looks
User2: Expected Freeze exceptions requests:
User13: there's a sync waiting for that
User13: the ruby bug
User2: User13 ok.
User13: I'll do it as soon as we unfreeze
User2: bug 541907: Add scripts to runcmd
User15: Launchpad bug 541907 in cloud-init "cloud-config should support some method for passing scripts" [Undecided,New] https://launchpad.net/bugs/541907
User2: that one would be nice to have
User2: We also might file Ffes for minor features hidden into globally bugfixing updates of php, munin, nut and bacula
User2: that's all from us.
User9: I recently commented on the bacula one (there's already a bug for it)
User2: User13 by "raising priority" I meant targeting to beta2.
User9: User2 thank you
User2: User13 but I see it's under control :)
User9: any questions to server team?
User9: [TOPIC] Mobile
User10: New Topic:  Mobile
User1: hi
User9: User1 o/
User1: [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
User10: LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
User1: so beta went quite well --- assuming that the x server crash we had is really the one that was fixed in last round
User1: unfortunately we couldnt verify because our QA had scheduled holiday today
User1: its bug 540477
User15: Launchpad bug 540477 in xorg-server "X restarted, but no .crash file" [Undecided,New] https://launchpad.net/bugs/540477
User1: which is probably dupe of bug 540256
User15: Launchpad bug 540256 in upstart "enter kills X when booting Live CD or w/cryptsetup with plymouth text plugin" [Critical,Fix released] https://launchpad.net/bugs/540256
User1: more on RC bugs
User1: we have quite a few fixes staged as you can see in report for after beta-1
User1: i decided to drop two bugs from RC list this week:
User1: bug 514253: qt4-x11 "[arm] needs porting to thumb2"
User15: Launchpad bug 514253 in qt4-x11 "[arm] needs porting to thumb2" [High,Won't fix] https://launchpad.net/bugs/514253
User1: seems that our -marm approach is good enough for the rest of issues left
User1: bug 457878: imx51 on board ethernet plug/unplug events not detected
User15: Launchpad bug 457878 in linux-fsl-imx51 "imx51 on board ethernet plug/unplug events not detected" [Medium,Won't fix] https://launchpad.net/bugs/457878
User1: i know our kernel peers are working on that, but i think we can live if this is still broken
User1: so if they get a fix i would still get that in
User9: User1 which means you'd need to manually click NM if you plug in a cable, as a workaround?
User1: right
User13: User1 yes, almost certainly a dup - Xorg.0.log.old shows it getting SIGQUIT which is the same crash path
User1: thanks!
User1: so two bugs i would like to get help for ;)
User9: http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html has two WIs left, can you please carry them over to beta-2?
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html has two WIs left, can you please carry them over to beta-2?
User1: bug 528887: maximus "maximus does not give default focus to newly started apps in combination with efl launcher"
User15: Launchpad bug 528887 in maximus "maximus does not give default focus to newly started apps in combination with efl launcher" [Medium,Triaged] https://launchpad.net/bugs/528887
User1: i would think dxteam or desktop team can probably help on that
User1: bug 528524: pulseaudio "Sound not working in all apps on dove"
User15: Launchpad bug 528524 in pulseaudio "Sound not working in all apps on dove" [High,Confirmed] https://launchpad.net/bugs/528524
User9: User1 can you talk to didrocks about 528887?
User1: basic stuff seems to work in kernel. if someone could ask questions there would be great
User1: we would certainly give all info on the pulseaudio bug that is needed
User1: User9 will do
User9: [ACTION] pitti to get people to investigate #528524
User10: ACTION received:  pitti to get people to investigate #528524
User1: its reprducible on i386 as the -efl launcher is there too ... so yeah
User1: spec front is still slowly moving
User1: i moved all items to beta-2 left
User1: total 8
User1: [LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-2.html
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-2.html
User1: only relevant for archive are the webservice ones
User9: looks good on that front, reasonable workload and enough time for more bug fixes
User1: yeah ;)
User1: unfortunately our team is often out of office due to sprints customers etc.
User1: but i think its still good workload wise
User9: User1 are the other thumb2 ports on track?
User1: the 3 left one? yes, we are working on them
User9: great
User1: its just 3, so that should be doable
User9: any other questions for mobile?
User1: we will do a mass give back for universe
User1: this weekend
User9: thanks asac!
User1: thanks!
User9: [TOPIC] Kernel
User10: New Topic:  Kernel
User4: here
User4: Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Beta-1 activity is summarised at the second URL below all now complete, a few items have been pushed out and appear under Beta-2 leah91@example.net.  The burndown chart for Beta-1 is at the third URL, and our burndown chart is at the fourth:
User4: [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
User4: [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
User4: [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04-beta-1.html
User4: [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
User10: LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
User10: LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04-beta-1.html
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
User4: Of the pushed out Alpha-3 items four have been postponed to M, two low priority items have been further pushed out to Beta-2, and two have patches in testing.  The items pushed out of Beta-1 are either investigative or basically complete and awaiting final test and upload.
User4: On the items pulled out on the agenda, the ureadahead optimisation work remains to be tested but is a small patch kernel side and does not impact any features.  The configuration review is complete and patches are out for review and expected to hit once the freeze is lifted.  The DRM reporting is now committed and again waits on the freeze lifting.  From the bugs, the EC2 logging bug looks to be a configuration issue and we expect to have a fix fo
User4: r it shortly, the other two bugs we have fixes commited and await the freeze to lift to upload them.
User4: None of the uploaded kernels have changed since the last meeting due to the freeze.  The ti-omap kernel has now been approved for FFe and MIR and awaits the freeze lifting to hit the archive.
User4: <done>
 * pitti caught up
User9: User4 workloads for beta-2 and final look very reasonable, great job
User4: mostly non kernel work too
User9: User4 did you hear a lot of feedback about the DRM backport?
User4: most of it has been positive.  generally less complaints
User9: it still seems to cause some troubles, but from my POV it seemed to have gone through quite well?
User3: I fear that most drm bugs are being attributed to plymouth up to this point
User4: we have one outstanding issue with powersave, which is looking like we have fixed and should come in soon
User3: we'll probably be getting better feedback in the coming weeks
User4: yeah until plymouth stops being the first barrier its hard to be tottally sure
User3: (hi everybody, welcome to beta1 :)
User9: User3 yay! congratulations
User3: User4 it has stopped being the first barrier
User9: that was a rather complicated birth
User4: general wisdom is that its not perfect but much better, and we continue to work on fixing issues as we see them
User3: User4 so please adjust any triaging assumptions accordingly :)
User4: slangasek, :) indeed ... X normally blame us anyhow
User9: any questions for kernel?
 * ttx highfives slangasek
User9: thanks apw!
User9: [TOPIC] desktop
User10: New Topic:  desktop
User9: User9 hello :)
User9: [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
User10: LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
User9: as usual, this has the details about weekly progress, spec status, and RC bug status
User9: Beta-1 WIs all done, one spillover spec: https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-gdmsetup
User9: http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html
User9: For Beta-2 we mostly have some cleanup WIs left, plus adding some much missed options to gdmsetup (already commited)
User9: http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-2.html
User10: LINK received:  http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-2.html
User9: Biggest missing feature/bug is that Gwibber currently stores account passwords in couchdb in cleartext(!), but should use gnome-keyring.
User9: We got a lot of bug fixes during this week, but are struggling a bit with the RC ones mentioned here. Martin will direct more attention to them.
User9: ->  "here" -> in the report, sorry for the semantic cut&paste error
User9: Called out in release team meeting invitation:
User9: desktop-lucid-xorg-multitouch: This hit us 1.5 weeks ago through a SABDFL override of FF, etc., and is currently diverting away Bryce.  The really intrusive bits (kernel driver, evdev patch, etc.) are in now, but this still needs better udev rules, test plans, and testing with wacom in particular.
User9: given how far it has come, I'm positive that it should work well by beta-2
User9: bug 456468 has turned out from "apparently simple" to "almost impossible to solve cleanly"
User15: Launchpad bug 456468 in network-manager-applet "upgrade triggers nm-applet "resource not found" ... missing icon "nm-applet-device"" [Undecided,New] https://launchpad.net/bugs/456468
User9: nm-applet picks up new icons during upgrade, tries to load them, and fails because the new GTK icon loader doesn't work with the old libc6 already in memory
User9: and we'd need to retroactively fix the old code to make it autorestart
User9: best workaround would be to restart it in update-manager; second best is to not do anything about it, it does not break the upgrade itself.
User9: we are still pondering what to do about it, but it might take a while
User9: We also collected a list of bugs which are not really RC, but which we want to fix for Lucid to be appropriately polished for an LTS release:
User9: http://www2.bryceharrington.org:8080/X/Reports/desktop-bugs/milestone-bugs.html
User10: LINK received:  http://www2.bryceharrington.org:8080/X/Reports/desktop-bugs/milestone-bugs.html
User9: User8 would you please do the Kubuntu bits?
User8: * Beta 1 (about to be) out the door, hugs to all who helped fix the various critical bugs there
User8: * New logo still being worked on by Canonical Design Team and being pondered over by Kubuntu people
User8: * https://wiki.ubuntu.com/Kubuntu/Todo (this page needs some updating, no new features expected)
User8: * Beta testing and some thourough bug triage have increased milestoned bugs marked as kubuntu to 32 http://tinyurl.com/yjybcx9
User8: * Bugs now need categorised and squishing, only 1 worrying me Bug:448705	"akonadi server doesn't start at login" which is essentially an upstream issue
User8: * tseliot is working on plymouth to KDM smooth transition support
User8: * doko fixed Qt on ia64 so build failures there now much reduced
User8: 10.04 documentation is due soon too, nixternal has been cracking the whip on that
User9: User8 so plymouth and kdm are at least on ceasefire terms now?
User8: User9 yes for beta plymouth dies before kdm starts, it's ugly but reliable
User11: It's not smooth, but at least it boots.
User9: right, that's how it was expected to look likenow
User9: any questions about desktop?
User3: when will my firefox fonts stop shimmering :)
User3: (sorry, know that asac already addressed this)
User9: ah, you hit a sore point there..
User9: User3 it's as high on the radar as I can put it; cf. "We got a lot of bug fixes during this week, but are struggling a bit with the RC ones mentioned here. Martin will direct more attention to them."
User9: but at least we are in 100% bug fixing mood now
User9: (flush unapproved, and you'll get a lot of love :) )
User3: User9 do you know if ccheney has an OOo upload scheduled anytime soon?  I see a few critical bugs accumulating there, with fixes known
User9: I don't know, I'll ask him
User9: in particular the arm crash should have a working patch now, too
User9: we need to get that out
User9: (asked)
User3: no other questions from me
User9: we ought to do that by next week, now that the freeze is behind us
User9: [TOPIC] DX
User10: New Topic:  DX
User9: User17 bonsoir
User17: hi
User17: so here is the short report: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
User3: [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
User10: LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
User17: so on the me menu the 2 potential changes tracked from last week are now been postponed to L+1
User3: User17 I've been seeing a bug recently where indicator-sound tells me things are muted when they aren't; is this bug known?
User3: (glad to see the mousewheel issue is tracked, I was going to be filing that one soon :)
User17: some pending fixes however are also quite invasive, so we' ve discussed filing for a proper FFE with seb128
User17: User3 that one is kind of known
User17: User3 we have an autobuild system that was producing packages with the wrong version number
User17: User3 and afawct it was due to an old version being build (but only in an internal ppa)
User17: User3 the lucid version has had a fix for that for some weeks, and ronoc uploaded a version yesterday with a version number that should prevent this packaging bug from re-appearing
User9: the mute bug seems to be random these days, but I still get it in 70% of the cases, too, if you need me to help with debugging
User17: hope this is the same bug, or else we have another issue
User3: User17 hmm, the mute bug I see is with the lucid package; do you mean that the wrong package is in lucid right now?
User17: User9 yeah, if you can reproduce it with lucid packages, we definetly want to know
User3: I'm not using the ppa
User9: User17 ok, I'll file one then
User17: so it' s a regression and we need to fix that
User3: ok
User17: User9 yes, please
User9: [ACTION] pitti to file bug about sound indicator being muted
User10: ACTION received:  pitti to file bug about sound indicator being muted
User17: we' re monitoring a couple of lists of bugs triaged with the desktop team
User17: please assign to canonical-dx-team initially, and we' re then re-dispatching to individuals
User9: ack
User17: https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs?field.assignee=canonical-dx-team
User9: I guess the "disable twitter input field without configured accounts" should also be there
User17: the rest is already assigned to particular developers
User17: well, so this one is the one with the invasive code change
User17: ie, i' m now monitoring the service, so that required a g_object' ification with signal monitoring
User17: i agree it should be reviewed as an FFE maybe; we're conducting code reviews for all code that land in trunk already though
User9: couldn't it just update its UI when you configure accounts?
User9: anyway, let's discuss off-meeting
User17: we've released a couple of bug fixes also as part of our thursday uploads
User17: User9 ok
User9: User17 those are likely stuck in unapproved then
User9: so let's re-test those next week
User17: New releases for this week: see DesktopExperienceTeam/LucidWeeklyReleases
User17: Of note:
User17: indicator-me-0.2.5-0ubuntu1: bug fixes, hide missing options, show avatar in menu, fixes 525951
User17: indicator-session-0.2.5-0ubuntu2: properly lock the screen when switching to another session, also respect lockdown settings
User17: indicator-sound-0.1.3-0ubuntu1: mousewheel support fix (#521046 & #523369)
User17: libindicator-0.3.6-0ubuntu1: enforces the proper icon size
User17: yes, some are still in the queue
User17: while other have already made it to the archive
User3: I'll be flushing the queue after the meeting
User17: no worries
User17: a heads up for the icon size thing too
User9: just wanted to point out to davidbarth that some of the fixes are not really "in" yet, and thus folks might file a lot of dupes for beta-1 installations
User17: we' ll have a patch next week to enforce the icon size in the indicator menus too, not only on the panel
User17: User9 ok
User3: ok; anything else for DX?
User9: any other questions to DX?
User3: (pitti has to take off, so we'll switch chairs now)
User9: User17 merci beaucoup
User9: #endmeeting
User10: Meeting finished at 12:11.
User17: User9 thanks
User3: #startmeeting
User10: Meeting started at 12:11. The chair is slangasek.
User10: Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
 * pitti hands microphone to slangasek
User3: thanks :)
User3: [TOPIC] Foundations Team
User10: New Topic:  Foundations Team
User3: User13 hi
User13: Plymouth was a bit hair-raising in the run-up to beta-1, but I think we're in much better shape now due to some incredibly tedious strace-level debugging (thanks to Keybuk).
User13: We had a substantial flow of bugs this week from ISO testing.  My general impression is that the bulk of the ones that have ended up milestoned are fairly small, relative to how things usually are ...
User13: The big ISO testing bugs were: (1) LVM+encryption failure (looks like a race, in progress); (2) Wubi dropped to GRUB shell (fixed); (3) package installation failure in oem-config (unknown); (4) GRUB failures on LVM/RAID (in progress); (5) a collection of tractable-looking Kubuntu bugs
User13: Spec overflow (all moved to beta-2):
User13: * foundations-lucid-supportable-binaries: 100% overflow, but archive-side and shouldn't need (many) uploads
User13: * foundations-lucid-release-collaboration-with-debian: 50% overflow, specifically Java - at this point I'm not concerned
User13: * foundations-lucid-computer-janitor: 25% overflow, one crash bug awaiting code review
User13: Beta-2 work items: The only one I'll be at all concerned about not making it is vga16fb handling in Plymouth, which I understand to be in progress.
User13: Bug 368060 is getting very slowly pushed up the design hill.
User13: parted 2.x's new use of the BLKRRPART ioctl rather than BLKPG is causing several milestoned bugs.  Planning to unpick and revert this on a devil-you-know basis.
User15: Launchpad bug 368060 in ubiquity "Map of Kashmir when selecting the timezone is incorrect" [High,Triaged] https://launchpad.net/bugs/368060
User13: Of bugs milestoned to beta-2, based on a very rough count of which ones are for the Foundations team, we have 30 <= triaged, 5 in progress, and 14 fix committed.
User13: Other than that, business as usual ...
User13: --
User3: ok
User3: that all aligns with my own understanding of the last couple of days, so no questions :)
User3: anyone else?
User3: [TOPIC] Security Team
User10: New Topic:  Security Team
User3: User13 thanks
User3: jdstrand: hi
User13: oh, and thanks for dealing with the knock-on effects of beta-1 running late!
User3: User13 better to get our "exciting" milestone out of the way before release day :)
User3: well, no jdstrand I guess
User3: the one milestoned bug has a merge request on it, which kees reviewed but I don't think understood the implications of since that's not our typical workflow... :)  I've prodded, so I guess that'll move soon
User3: [TOPIC] MOTU
User10: New Topic:  MOTU
User3: User11 around?
User11: Yes.
User3: hello
User11: Seems like FFe's are getting reviewed.
User11: I didn't see any more Ruby/Ocaml/ghc6 requests, but I'm not sure if we're done.
User3: I hope to help with the FFe backlog tomorrow
User11: Still nervous about Python and 2.6 compatibility, but nothing new.
 * slangasek nods
User18: User9 sorry, wasn't around. For Edubuntu, I'm still waiting for the new logo to be done by Canonical Design team. Once I have it, we'll update the relevant artwork (usplash, website, maybe ubiquity).
User3: User18 have they given you a due date for that new logo?
User11: On a more general note, it looks like Debian will move to boost 1.42 for Squeeze.  I made an executive decision not to care (and updated the notes in the debian cooperation spec)
User11: That's all.
User3: User11 yes, I saw - thanks for that
User3: oh, speaking of FFes, a reminder to folks that as process bugs, FFes need to be set to "New" if you expect the release team to know they need looked at
User3: I've caught sight of a couple coming over to us as 'triaged' or 'in progress', and am concerned that we may be overlooking some requests this way
User3: (if the FreezeExceptionProcess page doesn't already mention this, I'll update it to do so)
User3: any other questions for MOTU?
User3: #endmeeting
User10: Meeting finished at 12:22.
User3: thanks, everyone!
User13: the wiki doesn't appear to say this
User18: User3 it was supposed to be something like two weeks ago (at least for some temporary artwork) ... I've been regularly pinging iainfarrell about it ;) We basically needed the "e" and the "d" and then make a new logo out of that
User19: User3 aren't the .04s the release weeks that always go relatively smoothly anyway?
User20: User18 We're awaiting final sign off on the font
User3: User20 who are you waiting for sign-off from?
User11: User18 Kubuntu didn't get just a "K" yet, so I wonder how long two letters takes ...
User20: still don't have it I'm afraid but as soon as I do there will be such a cheer that you'll hear it from there
User19: User18 err, it probably isn't usplash artwork that needs updating ;-)
User20: User11 They take a long time, type face development is both time consuming and expensive
User20: so it's important we get it right
 * slangasek reads Keybuk's comment, finds a piece of wood, and knocks on it hard with his head
User11: User20 Certainly.
User18: User19 doh, sorry, yeah, plymouth ;)
User20: everything is dependant on this so keep checking in and as soon as we have it I'll be contacting the people who came in before freeze
User20: and we'll update the guideline pages on the wiki
User20: should be early next week at the latest but I've said that before
User20: so please bear with us
User11: User20 Which would be an indication the process was started later than it should have been.
User20: User11 which is an indication that decisions by those that get to make them have taken longer than they should have
User20: we started in good time
User20: but have asked for more attention to be paid to certain aspects and this has caused delay
User11: User20 All that's invisible to the community.
User19: User18 writing plymouth themes is fun
User19: I have my dancing monkey theme all ready for the next release ;-)
User18: User19 hehe ;)
User19: of course, I'm rather assuming that it will be "monkey" there, but I'm rooting for the monkey!
User21: User19 I want to see what you'll do for might midge
User21: mighty even
User3: User20 who are you waiting for sign-off from at this point?
User20: User3 At the moment we've selected a direction and are awaiting some final amends from the developers which will then be signed off by Mark
User20: this won't give us a complete character set
User20: but enough for the logos
User20: and it'll be an almost complete roman character set
User20: once we're happy with those the other faces should come reasonably quickly but Mark is very keen not to rush this work so as I said, as soon as I have updates I'll let you know
User3: ok
ubuntu-meeting
Ubuntu IRC