[09:50]  * randa-afk is away: Gone away for now
[09:50]  * randa_ is back.
[15:55]  * slangasek waves
[15:56] <czajkowski> slangasek: happy it's friday :)
[15:57] <ScottK> Right.  It's about that time.
[15:57] <slangasek> hmm, is it?  wonder where Thursday went...
[15:58] <ScottK> No idea.  I was up until 2:30 local do data analysis on a $WORK project and then back up before 8.
[15:58]  * ScottK recalls he needs more coffee.
[15:59] <slangasek> I have you beat, it's still not 8 here ;)
[15:59] <pitti> o/
[15:59]  * slangasek waves
[16:00]  * asac waves
[16:00]  * marjo waves
[16:00] <slangasek> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is slangasek.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <ttx> o/
[16:01] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-04-09
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-04-09
[16:01] <slangasek> [TOPIC] actions from previous meetings
[16:01] <MootBot> New Topic:  actions from previous meetings
[16:01] <slangasek>   * rickspencer to ask designers about new Edubuntu logo
[16:01] <slangasek>   * slangasek, asac to discuss omap plans for 10.04 (DONE, discussed with davidm)
[16:01] <slangasek>   * doko to grep the archive for codecs.open in python code, to find other packages broken by http://bugs.python.org/issue691291
[16:01] <slangasek>   * ScottK, slangasek to review python sync/merge candidates (INPROGRESS)
[16:01] <asac> slangasek: from what i understood you discussed high level bits on omap with david ... more detailed bits are now in RC bug section.
[16:01] <slangasek>   * slangasek to document bug #528155 for beta2 errata (DONE)
[16:02] <slangasek>   * rickspencer3 to figure out what package needs changed for bug #357673 (DONE)
[16:02] <asac> ack
[16:02] <slangasek> pitti: no rickspencer?
[16:02] <pitti> he's on vacation today
[16:02] <slangasek> pitti: ok
[16:03] <slangasek> asac: right; my immediate concern was "what are the deliverables and the support expectations", which hadn't been discussed up until now, but I have those answers now
[16:03] <pitti> slangasek: anyway, I looked at the bug, too, and triaged it
[16:03] <slangasek> doko confirmed to me that codecs.open is on his todo list, but that he was waiting for IS
[16:04] <slangasek> doko: ^^ what is it you needed installed on people.c.c to do this grep?  is there an RT ticket I can +1? :)
[16:05] <slangasek> [TOPIC] QA Team
[16:05] <MootBot> New Topic:  QA Team
[16:05] <marjo> slangasek: i have a few items today
[16:05] <marjo> * Hardware testing
[16:05] <marjo> Automated Tests
[16:05] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:05] <marjo> Netbooks:
[16:05] <marjo>    passed:   13 (93%) failed:    0 ( 0%) untested:  1 ( 7%)
[16:05] <marjo> Laptops:
[16:05] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:05] <marjo>    passed:   44 (94%) failed:    0 ( 0%) untested:  3 ( 6%)
[16:05] <marjo> Servers:
[16:05] <marjo>    passed:   65 (94%) failed:    0 ( 0%) untested:  4 ( 6%)
[16:05] <marjo> Desktops:
[16:05] <marjo>    passed:   12 (100%) failed:    0 (  0%) untested:  0 (  0%)
[16:05] <marjo> Manual Tests
[16:05] <marjo> http://people.canonical.com/~fader/milestones/lucid/beta1.html
[16:05] <MootBot> LINK received:  http://people.canonical.com/~fader/milestones/lucid/beta1.html
[16:05] <marjo> Passed: 19 (31%) Failed: 12 (20%)  Untested: 30 (49%)
[16:06] <ttx> marjo: beta1.html ?
[16:06] <slangasek> those are stale test results though, yes?
[16:06] <slangasek> (the beta1)
[16:06] <marjo> why stale?
[16:06] <fader_> slangasek: alexmoldovan has been plowing through those since beta 1 came out, but he is only available in the lab 3 days per week
[16:06] <marjo> slangasek: oh yes, because we had already started those
[16:07] <doko> slangasek: it is installed, the ticket is closed
[16:07] <fader_> slangasek: per the conversation we had at alpha 3, you asked that we stick with one image rather than test the daily builds
[16:07] <slangasek> marjo: stale because it says "beta1", and we would want confirmation with beta2
[16:07] <marjo> slangasek: understood
[16:07] <slangasek> fader_: how does "beta1" differ from "current", then?
[16:08] <fader_> slangasek: Not sure I understand... these are manual tests executed on the hardware on the beta 1 image rather than the current
[16:08] <slangasek> ah, right
[16:08] <fader_> At alpha 3 time we were doing the daily images for each day, but you had asked that we stick to one consistent image
[16:08] <marjo> Lucid Beta 2 Test Report
[16:08] <marjo> 9th April 2010
[16:08] <marjo> = Summary =
[16:08] <marjo> == Test Coverage ==
[16:08] <marjo> Image Coverage: 100%
[16:08] <marjo> Mandatory Testcase Coverage: 207/207 = 100.00
[16:08] <marjo> Optional Testcase Coverage: 9/18 = 50.00
[16:08] <marjo> [16:08] <marjo> 25 Test Failures
[16:08] <marjo> Failure Rate 25/216 = 11.57
[16:08] <marjo> == Serious bugs found in ISO testing status ==
[16:09] <marjo> http://people.canonical.com/~marjomercado/isotestingbugs.html
[16:09] <MootBot> LINK received:  http://people.canonical.com/~marjomercado/isotestingbugs.html
[16:09] <marjo> thx to everyone who helped us achieve such nice test coverage on beta 2!
[16:09] <slangasek> fader_: yes, because we were getting test failures due to known transient problems in the dailies; now we seem to be having the opposite problem, in that half these failures are annotated as known-fixed in newer builds :)
[16:10] <slangasek> anyway, assuming these will be re-tested soon with beta2, that's ok
[16:10] <fader_> slangasek: Yeah, the majority of the bugs we found are fixed in the dailies at this point.  We are figuring this out and trying to hit a happy medium... it's all new process :)
[16:10] <fader_> (and alexmoldovan has been awesome about testing and re-testing on dailies :) )
[16:10] <marjo> == Bugs summary ==
[16:10] <marjo> [16:10] <marjo> 60 bugs unfixed
[16:10] <marjo> Critical - 1
[16:10] <marjo> High - 14
[16:10] <marjo> Medium - 7
[16:10] <marjo> Low - 3
[16:11] <marjo> Undecided - 35
[16:11] <marjo> [16:11] <marjo> 12 bugs fixed
[16:11] <marjo> High - 7
[16:11] <marjo> Medium - 1
[16:11] <marjo> Undecided - 4
[16:11] <slangasek> marjo: I'm concerned about the low "optional testcase" coverage - from my end, the intent of optional testcases is to identify tests we need to make sure are run against *some* image as part of a release, but don't need to be run for *every* image where they apply
[16:12] <marjo> slangasek: understood; as you know priority is always to get 100% on mandatory, then go for optional
[16:12] <slangasek> is there a list of the optional testcases that weren't covered, and does the QA team have time to follow those through this week so we cover our blind spots?
[16:12] <slangasek> this week->next week
[16:12] <marjo> but will work with testing team to see how to get higher coverage on all
[16:12] <marjo> slangasek: yes, will do retrospective
[16:13] <slangasek> I don't mean retrospective, I mean that those missing test cases should still get tested before RC is upon us
[16:13] <marjo> slangasek: ok, i misunderstood
[16:13] <marjo> yes, will see what can be done
[16:14] <slangasek> [ACTION] marjo to make sure the outstanding optional testcases for beta2 get tested this week
[16:14] <MootBot> ACTION received:  marjo to make sure the outstanding optional testcases for beta2 get tested this week
[16:14] <marjo> Lucid Quality Status Report
[16:14] <marjo> 20 days left and 315 bug tasks to fix.
[16:14] <marjo> Barring no new work we need to fix 16 bug tasks a day now.
[16:14] <marjo> The focus of bug fixing should be on the following tasks:
[16:14] <marjo>         The 6 Critical bug tasks.
[16:14] <marjo>         The 30 bug tasks that might cause a regression in Lucid.
[16:14] <marjo>         The 113 High bug tasks.
[16:14] <marjo> The Canonical Desktop Team needs to deal with 18 bug tasks.
[16:14] <marjo> Martin Pitt is the most overtasked with 9 bug tasks.
[16:14] <marjo> Martin Pitt is rockin' with 76 bug tasks fixed!
[16:14] <marjo> Yesterday's hero was Michael Vogt with 4 bug tasks fixed!
[16:15] <slangasek> not so bad
[16:15] <marjo> Spec Status
[16:15] <marjo> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-2.html
[16:15] <marjo> All completed except:
[16:15] <marjo> Identify and implement improvements for finding bugs that affect hardware
[16:15] <marjo> 1. Write up a nice README to document existing HWDB scripts we have, what they do, and how to use them: TODO
[16:15] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-2.html
[16:15] <marjo> 2. Send an email to the platform team ml for anyone who may be interested: TODO
[16:15] <marjo> Will retarget to end of release.
[16:15] <pitti> hm, given that the "need to fix #n bugs per day" keeps rising, we should perhaps take off some and move them to SRUs
[16:15] <pitti> we won't be able to keep up at this pace
[16:15] <marjo> slangasek:yes, must keep the focus up
[16:15] <slangasek> there are a number of bugs currently milestoned for final that I'm sure are not going to make it; we need to be explicitly deferring some of those and focusing on the others
[16:15] <slangasek> in particular, the current kernel bug load is completely unrealistic
[16:15] <marjo> slangasek: agree
[16:16] <marjo> slangasek: but as you know, jfo and team have been quite busy resolving bugs
[16:16] <pitti> marjo: hm, I have 9 RC bug tasks assigned? I'm not aware of that..
[16:16] <slangasek> pitti: the "bugs per day" was actually stable all last week; then we had Easter + freeze :)
[16:17] <pitti> https://bugs.edge.launchpad.net/~pitti/+assignedbugs?orderby=status has 4 lucid-targetted tasks..
[16:17] <marjo> pitti: will double check & modify report
[16:18] <pitti> marjo: those are lucid-targetted bugs only? or RC bugs? (lucid and high/critical)?
[16:18] <marjo> pitti: yes, lucid only
[16:18] <pitti> marjo: I'm just curious what these numbers refer to
[16:18] <pitti> marjo: ah, thanks
[16:18] <marjo> pitti:otherwise, too much noise
[16:18] <pitti> marjo: LP helpfully duplicates lucid-targetted bugs in lists ..
[16:18] <marjo> need to focus on lucid
[16:18] <ttx> pitti: shouldn't RC be "lucid and targeted to ubuntu-10.04" ?
[16:19] <pitti> ttx: https://wiki.ubuntu.com/RCBugTargetting says targetting and >= high
[16:19] <ttx> pitti: ok thx
[16:19] <pitti> but targetting the ones to ubuntu-10.04 which we want to fix by final makes sense, too
[16:20] <slangasek> if you intend to fix a bug for 10.04 final, please make sure the milestone is set too
[16:20] <marjo> slangasek: that's all from QA team
[16:20] <pitti> ttx: the un-milestoned ones automatically become SRU targets
[16:20] <slangasek> marjo: right, thanks!
[16:20] <slangasek> [TOPIC] Server Team
[16:20] <MootBot> New Topic:  Server Team
[16:20] <slangasek> ttx: hi
[16:20] <ttx> hey
[16:20] <ttx> Updated status @ https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:20] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:20] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:21] <ttx> 3 lucid bugs targeted to ubuntu-10.04:
[16:21] <ttx> bug 551544
[16:21] <ttx> bug 556343
[16:21] <ttx> bug 556996
[16:21] <ttx> (just fixed)
[16:21] <ttx> all assigned and being worked on
[16:21] <ttx> See report for the other lucid-targeted bugs, most of them have now been assigned
[16:22] <ttx> We expect a surge in bug reports, as server users usually don't test before the last beta
[16:22] <ttx> so the list is expected to change
[16:22] <slangasek> ttx: bug #551544> possibly simpler to just get this fixed in upstart for release; can you make sure mathiaz talks with Keybuk about this?
[16:22] <slangasek> (bug #552786 is the corresponding upstart bug)
[16:22] <ttx> slangasek: yes
[16:23] <ttx> We have one team member assigned to triage of new server bugs every day, so that we don't lose the important RC one
[16:23] <ttx> Other questions on the bugs side ?
[16:23] <ttx> Moving on to Specs...
[16:23] <ttx> Beta2 postmortem:
[16:24] <ttx> Some wo'rk items were postponed:
[16:24] <ttx> server-lucid-apt-mirror-ec2: 1 WI still blocked on IS delivery, but imminent
[16:24] <ttx> server-lucid-puppet-uec-ec2-integration: testsuite enablement, documentation
[16:24] <ttx> server-lucid-uec-testing: multinetwork testing automation still work in progress
[16:24] <ttx> server-lucid-id-mgmt-reference-env: deferred (was Low priority)
[16:24] <ttx> That leaves us with a few work items for final, mostly unaffected by FinalFreeze
[16:25] <ttx> http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04.html
[16:25] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04.html
[16:25] <ttx> ^ see above url for details
[16:25] <ttx> Bugs affecting server in other teams:
[16:25] <ttx> The only one I could find is one reported in ISO testing about RAID/ext3
[16:25] <ttx> bug 557429
[16:26] <ttx> Other issues affecting release:
[16:26] <ttx> Two lucid bugs would probably need FFes to get fixed: bug 392759 and bug 533029
[16:26] <ttx> Expect some noise from there if not already done
[16:26] <ttx> That's all for us
[16:27] <ttx> questions ?
[16:28] <slangasek> ogasawara: bug #557429 is marked as a kernel bug; and it's a potential data loss bug *caused* by RAID1, so should be fixed for final if at all possible - what further triaging is needed there?
[16:29] <ogasawara> slangasek: I'll take a look and get it into shape if needed
[16:29] <slangasek> [ACTION] ogasawara to triage bug #557429 for final
[16:29] <MootBot> ACTION received:  ogasawara to triage bug #557429 for final
[16:29] <slangasek> thanks
[16:29] <slangasek> no other questions here, anyone else?
[16:29] <slangasek> [TOPIC] Mobile Team
[16:29] <MootBot> New Topic:  Mobile Team
[16:29] <slangasek> ttx: thanks
[16:29] <slangasek> asac: hi
[16:29] <asac> hi
[16:29] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:29] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:30] <asac> so webservice office took a bit, but we now have the copyright/trademark issues sorted for artwork
[16:30] <asac> webservice email is in the archive too ... MIR is coming ...
[16:30] <asac> two main things are now troubling us:
[16:30] <asac> * omap kernel and initial enablement
[16:31] <asac>  -> making progress, but we didnt get to flashing out all the user space issues in the image yet
[16:31] <asac> * openoffice build regression
[16:31] <asac>  -> really, sad, but ooo now fails to build after recent updates
[16:31] <asac> we are currently investigating to find the cause for this
[16:31] <asac> i made a omap section for rc bugs on the status page
[16:31] <asac> so you get the issues we know about in one place
[16:32] <asac> so besides kernel we expect to touch flash-kernel and partman-uboot to teach it omap
[16:32] <asac> imx51 and dove images are in good shape though ... so no headaches on that front ;)
[16:32] <slangasek> asac: I noticed the other day from http://people.canonical.com/~ubuntu-archive/testing/lucid_outdate.html that there's an armel-specific build failure in main that I thought was on the porting bug list but apparently isn't - libtunepimp?
[16:33] <asac> yes, thats one of the 3? ftbfs we have on our list for this week
[16:33] <asac> cant tell more about it. i dont think its thumb2 related -- otherwise it would have been on our list
[16:34] <asac> also we will do a mass give back on universe one more time to pick up a few things that probably build now
[16:35] <slangasek> when you say it's "on your list" - it's not on the release status list, and it's not targeted/milestoned for 10.04?
[16:35] <slangasek> I'd like visibility into whatever list it's actually on, please :)
[16:35] <asac> yes, that should get a bug
[16:35] <asac> sorry
[16:35]  * asac goes and files
[16:37] <asac> ok done
[16:37] <asac> 559338
[16:37] <slangasek> thanks
[16:38] <slangasek> anything else?
[16:38] <asac> not from my side
[16:38] <ogra> i'll need to touch some installer bits for omap next week (but they are covered as bugs)
[16:38] <ogra> just to warn :)
[16:38] <asac> ogra: more than those we have on the page?
[16:38] <asac> ;)
[16:38] <ogra> i hope not
[16:39] <asac> ok
[16:39] <ogra> but not having an image that gets to a full installation yet makes it hard to predict
[16:39] <asac> right. i mentioned that above
[16:39] <ogra> i might hit issues that arent on the list yet
[16:39] <slangasek> asac: I saw plars had just retargeted bug #542662 to final; in a previous meeting I got the impression that this was not critical-path for omap, is that correct?
[16:39] <ogra> drop it please
[16:40] <asac> slangasek: yes. we are ok to not have that
[16:40] <slangasek> ok
[16:40]  * asac does that
[16:40] <ogra> we want it in the archive but we dont use it in 10.04
[16:40] <asac> done
[16:40] <ogra> it just enables users of such HW to reflash their nand with a package from us
[16:41] <asac> ack. ok. any other questions?
[16:42] <slangasek> asac: last question, what needs to happen to get these thumb2 porting bugs sorted?  Is there anything people outside Mobile can do to help?  The bug descriptions are all very brief and the page they link to doesn't provide much more information, so I wasn't able to get any traction on the one I looked at
[16:42] <asac> slangasek: hmmm
[16:42] <asac> https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList has quite detailed info
[16:42] <asac> also
[16:42] <asac> https://wiki.ubuntu.com/ARM/Thumb2PortingHowto
[16:43]  * ogra thought those links were in the bugs by default
[16:43] <asac> slangasek: for main we just have xine-lib left ... which i am reviewing/working on now
[16:43] <asac> ogra: not sure if we linked the portinghowto
[16:43] <asac> but its linked from the reviewlist page
[16:43] <ogra> ah
[16:43] <asac> slangasek: which package are you interested in?
[16:43] <slangasek> maybe I was having a bad reading day when I tried to look
[16:44] <slangasek> asac: I'm not interested in any package, I'm interested in having the bugs resolved since they seem to be dragging on :)
[16:44] <asac> slangasek: yeah. one left now ;)
[16:44] <slangasek> didn't you just mark xine-lib as wontfix?
[16:44] <slangasek> upx-ucl is still open, though
[16:45] <asac> slangasek: sorry mixed those
[16:45] <slangasek> ok
[16:45] <asac> upx-ucl is what i am looking at ;)
[16:45] <slangasek> then I guess they're in progress, so I don't need to stick my nose in
[16:45] <asac> yep
[16:45] <slangasek> any other questions for Mobile?
[16:45] <slangasek> [TOPIC] Kernel Team
[16:45] <MootBot> New Topic:  Kernel Team
[16:45] <slangasek> asac: thanks
[16:45] <slangasek> ogasawara: hi
[16:45]  * apw is here
[16:46] <asac> thanks
[16:46] <slangasek> apw: hi
[16:46] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  The burndown chart for Release is at the third URL, and our burndown chart is at the fourth.  There are a couple of items outstanding in Beta-2 which either need closing or pushing out, none release critical:
[16:46] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:46] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04
[16:46] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04.html
[16:46] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:46] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04
[16:46] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04.html
[16:46] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:46] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:46] <apw> On the items pulled out on the agenda: the work remaining on AppArmor is upstreaming and not release criticical; the configuration review waits on the configuration report which is also not release critical.  Of the bugs a number have fixes in testing, the remainder are progressing.
[16:46] <apw> We are planning a kernel upload for the main distro kernel today, this will carry some debian installer changes for XEN netboot images which need uploading to test completely.  This upload will also carry a stable update.  We likely will have one final upload early next week carrying a few stray fixes.

[16:47] <slangasek> apw: and next week's upload is the last before final?
[16:47] <apw> slangasek, yes thats the plan
[16:47] <apw> want you to have the longest run possible to the tape
[16:48] <slangasek> apw: bug #542660 seems unlikely to make it - should that one be marked as deferred to SRU?
[16:48] <apw> yes i think we are likely in that position on that one, its looking like a large change
[16:48] <slangasek> also bug #543617 looks risky for a last-minute change
[16:49] <apw> slangasek, i am told the change is very simple, so we may do it
[16:49] <apw> essentially 'sync; umount' works
[16:49] <slangasek> hmm, ok
[16:49] <apw> and umount on its own does not ... so if we can simulate that it may be ok
[16:49] <apw> else we'll have to wait for upstream to think more on why its not working as is
[16:50] <jdstrand> that bug is evil
[16:51] <apw> yeah has had us thinking hard for some time at that
[16:51] <apw> slangasek, to move something to sru i assume the approved milestone is lucid-updates
[16:51] <slangasek> apw: yes
[16:51] <apw> thanks
[16:51] <slangasek> no other kernel questions here; anyone else?
[16:52] <slangasek> [TOPIC] Desktop Team
[16:52] <MootBot> New Topic:  Desktop Team
[16:52] <slangasek> apw: thanks
[16:52] <slangasek> pitti: ohai
[16:52] <pitti> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:52] <pitti> ork items: Beta-2 items all done; just three WIs left for final, of which two do not affect the distro (Launchpad bug filing page update, design review of simple-scan), and the third is to disable the "File a bug" menu entry, which is prepared, but should happen only before the release candidate.
[16:53]  * pitti tosses a 'W' to the beginning
[16:53] <pitti> RC bugs: they keep comin', and we now also explicitly added the UbuntuOne bugs (which the U1 team is working on), but we had a good turnover this week and fixed 9, and further 5 are "fix committed". Details are on the wiki page
[16:53] <pitti> 2 RC bugs that we have serious trouble with: bug 507062 (investigation started, hoping that upstream will give some hints), and bug 447431 (was believed to be fixed for some time, but confirmed again recently; Chris will continue to investigate, now that his RC bug list has dropped dramatically)
[16:53] <pitti> desktop-lucid-openoffice: 3.2.1 was not released in time for Lucid final, but 3.2.0 is considered "good enough"; we'll provide 3.2.1 as an SRU
[16:55] <slangasek> pitti: bug #527138 - AIUI thunderbird is /not/ done, the latest comment on the bug as of this morning was that the thunderbird-dev package is still missing a piece needed to allow packages to build against it?
[16:55] <pitti> slangasek: oh, hmm; I'll have a look at this and reopen then
[16:56] <slangasek> OOo 3.2.1 as an SRU - that's going to fit in the normal SRU policy, or are we stretching the definition to make that work?
[16:56] <pitti> slangasek: that remains to be seen, as it's not released yet
[16:56] <pitti> but I guess it'll involve some stretching
[16:56] <slangasek> :/
[16:56] <pitti> perhaps s/we'll provide/we'll look at/
[16:57] <slangasek> that would be nice :)
[16:57] <pitti> once it's released and we know what things changed, we have to review that in detail
[16:57] <pitti> slangasek: related to that, due to GNOME's slightly chagned release cycle, we can't put 2.30.1 into lucid final
[16:57] <pitti> so we'll do some git snapshots early next week for the most important packages
[16:58] <pitti> in hardy we had a SRU policy extension for GNOME point releases
[16:58] <pitti> I think we should discuss applying that to lucid as well
[16:58]  * ScottK would like to do that for KDE too.
[16:58] <slangasek> agreed
[16:58] <ScottK> (in general, but particularly for Lucid)
[16:58] <pitti> i. e. we'll still review the changes, of course, but we might allow things like updated translations or harmless build system changes, etc.
[16:58] <slangasek> should that be discussed at UDS?
[16:58]  * doko would like to see this for OpenJDK too
[16:58] <pitti> so ideally 10.04.1 would have GNOME 2.30.2 or .3, and the new OO.o
[16:59] <pitti> doko: yes
[16:59] <pitti> slangasek: makes sense
[16:59] <slangasek> pitti: can you get it on the UDS agenda?
[16:59] <pitti> we have traditionally put much more effort into SRUs for LTSes
[16:59] <pitti> slangasek: yes, will do
[16:59] <slangasek> [ACTION] pitti to get discussion of SRU extension for GNOME, KDE, OOo, OpenJDK point releases on UDS agenda
[16:59] <MootBot> ACTION received:  pitti to get discussion of SRU extension for GNOME, KDE, OOo, OpenJDK point releases on UDS agenda
[16:59] <pitti> seb128: want to do the thawing topic, or shall I?
[17:00] <seb128> I wanted to raise again queue flushing on friday after freezes
[17:00] <seb128> I say again because I think it was discussed before
[17:00] <seb128> is there anything we can do to avoid having ton of updates landing to late to be tested before weekend?
[17:01] <slangasek> seb128: was that the case this time that things landed too late to be tested?
[17:01] <seb128> ie the half a day delay between beta2 and queue review there bring us in having updates landing on friday evening
[17:01] <seb128> rather than on start of day
[17:01] <seb128> yes
[17:01] <slangasek> I would prefer not having to review anything in the queue, and be able to just flush it
[17:01] <seb128> if they had been flushed yesterday we would have got updates this morning european time
[17:01] <seb128> and the day to catch issues
[17:01] <slangasek> unfortunately, some people have been uploading things to the freeze queue in lieu of getting FFe approval
[17:01] <slangasek> which means the queue has to be sifted before accepting
[17:02] <seb128> who are those people and can we teach them to not do that?
[17:02] <seb128> at least main upload should know better...
[17:02] <ScottK> seb128: I don't think so, I think it's just a lot of stuff in the queue.
[17:02] <slangasek> I meant to include a note about this in the beta 2 freeze announcement to make it clear where the responsibility lies, but I failed to remember
[17:02] <seb128> uploaders
[17:02] <seb128> I mean those same people can upload directly after unfreeze
[17:02] <seb128> why would they upload things during freezes which are not good to go after unfreeze?
[17:02] <slangasek> seb128: well, it's *exclusively* main uploaders, as unseeded packages aren't frozen for beta
[17:02] <seb128> it doesn't make sense to me
[17:03] <slangasek> no, it doesn't make sense, it shouldn't be the practice, we should fix it - I just failed to send out the announcement beforehand and I saw several packages in the queue that this affected
[17:03] <seb128> hum ok, still seems weird to me that we have people doing non lucid suitable upload to lucid queue during a freeze
[17:03] <slangasek> if we message this more clearly next time, then there should be no problem with flushing immediately after beta
[17:03] <ScottK> Also I reviewed and accepted enough stuff to keep most of the builders busy most of the night.  I don't think it delayed much.
[17:04] <pitti> seb128: it's quite a common workflow for SRUs, but right, it sholdn't be for the devel release
[17:04] <seb128> pitti, right but you don't unflush queues for sru
[17:04] <seb128> the milestones freezes are supposed to end and things to go in
[17:04] <pitti> ok, so in summary I think we know where the problem is and have to fix it on a social level then
[17:04] <seb128> right
[17:05]  * ScottK hands seb128 a stick.
[17:05] <seb128> learning every day
[17:05] <seb128> I wouldn't have though some people uploaded cracks to lucid queue during freezes
[17:05] <seb128> thanks
[17:06] <pitti> no Kubuntu status update today, sorry; apparently Jonathan is on holiday
[17:06] <ScottK> I can give one
[17:06] <pitti> please
[17:06] <ScottK> Beta 2 went pretty well for Kubuntu.
[17:06] <slangasek> seb128: btw, the first packages left in the freeze queue, that I accepted yesterday before going to bed, were metacity and compiz which ended up in a build-dep loop, so compiz didn't build all night anyway :/
[17:06] <ScottK> It also looks like yesterday's ia64 build for qt4-x11 may succeed (well past where it failed).
[17:07] <ScottK> We even have powerpc live CD ISO's that aren't oversized.
[17:07] <seb128> slangasek, yeah, I noticed that today, unfortunate
[17:08] <ScottK> slangasek: Were there any Kubuntu questions I can answer?
[17:08] <pitti> ScottK: powerpc> wow - nice diet!
[17:08] <slangasek> ScottK: we seem to still be struggling to get Kubuntu all the way there on the installer side; things that I thought had been tested and working with earlier milestones failed again with beta2 - do we know why this is?
[17:08] <ScottK> I'm standing by to unseed OOo from KNR armel if it doesn't get sorted.
[17:09] <ScottK> slangasek: I don't know.  I think that the main community developer for the KDE front end has not had a lot of time lately.
[17:09] <ScottK> I agree it's an issue.
[17:10] <ScottK> slangasek: Since Riddell isn't here, let's give him an action to investigate.
[17:10] <slangasek> [ACTION] Riddell to investigate the lingering Kubuntu installer issues
[17:10] <MootBot> ACTION received:  Riddell to investigate the lingering Kubuntu installer issues
[17:10] <ScottK> Nice.
[17:10] <ScottK> Nothing else from me.
[17:10] <cjwatson> they're high on my radar as well.
[17:10] <slangasek> I wonder if Kubuntu daily ISO testing is called for there
[17:11] <slangasek> from now 'til RC
[17:11] <ScottK> We'd need to get some fixes in first.
[17:11]  * pitti EOR as well
[17:11] <slangasek> because part of the problem seems to have been that we think things are fixed, and then we start beta testing three days before milestone, and we find there are still issues
[17:12] <ScottK> Oh, I did do some Kubuntu Hardy -> Lucid testing and am pushing a few additional replaces for people who upgrade Ubuntu LTS -> LTS and have Kubuntu installed too.
[17:12] <ScottK> Right.
[17:12] <ScottK> Makes sense.
[17:12] <slangasek> ScottK: could you put out a call for testing to the Kubuntu community for this?
[17:12] <ScottK> slangasek: I can.
[17:12] <slangasek> [ACTION] ScottK to put out a call for Kubuntu daily ISO testing
[17:12] <MootBot> ACTION received:  ScottK to put out a call for Kubuntu daily ISO testing
[17:12] <slangasek> thanks
[17:13] <slangasek> I think that's it for desktop then, yes?
[17:13] <marjo> ScottK: if appropriate, please enlist ara's help
[17:13] <ScottK> marjo: Will do.
[17:13] <ScottK> slangasek: AFAIK, yes.
[17:14] <cjwatson> I'll make sure there's an installer upload today - it will include several Kubuntu fixes
[17:14] <slangasek> pitti: btw, desktop-lucid-xorg-multitouch still has some WIs marked for beta2, perhaps you overlooked those?
[17:14] <pitti> yes from my side
[17:14] <pitti> slangasek: oh? hm, it shouldn't, I'll check
[17:14] <slangasek> ok
[17:14] <cjwatson> at least five that I can quickly see
[17:14] <slangasek> [TOPIC] DX Team
[17:14] <MootBot> New Topic:  DX Team
[17:14] <pitti> slangasek: our WI tracker was empty the last couple of days..
[17:14]  * davidbarth waves
[17:14] <davidbarth> hi
[17:14] <slangasek> davidbarth: hello
[17:14] <davidbarth> relatively calm on the dx front
[17:15] <davidbarth> we're hoping to be the least of your worries now
[17:15] <davidbarth> some bugs fixed for beta-2: https://bugs.launchpad.net/ayatana/+milestone/ubuntu-10.04-beta-2
[17:15] <davidbarth> and this is what we have on the radar to the RC: https://bugs.launchpad.net/ayatana/+milestone/ubuntu-10.04
[17:16] <davidbarth> we'll mostly propose crasher fixes, and that's all
[17:16] <slangasek> 546650> well, that's fixed in Ubuntu, dunno if you want that task open upstream still for some reason
[17:16] <davidbarth> we're monitoring incoming bug lists with seb128 daily; so far so good
[17:16] <slangasek> I think I saw 451086 was also fixed in Ubuntu
[17:17] <davidbarth> on the dbusmenu-qt bug, agateau just confirmed that the fix is in and solves the issue
[17:17] <slangasek> great
[17:17] <davidbarth> that was: #548882
[17:17] <slangasek> so indeed, the least of my worries now :)
[17:17] <davidbarth> 2 wi still left in the blueprints: docs, meant as reminders
[17:17] <davidbarth> so well, i'm reminded, that was the point
[17:17] <slangasek> :-)
[17:18] <davidbarth> that's it mostly; questions?
[17:18] <slangasek> please carry them forward to final so that they continue to be useful as reminders
[17:18] <slangasek> no questions here
[17:18] <slangasek> anyone else?
[17:18] <davidbarth> slangasek: ok
[17:19] <slangasek> [TOPIC] Foundations Team
[17:19] <MootBot> New Topic:  Foundations Team
[17:19] <slangasek> davidbarth: thanks
[17:19] <slangasek> cjwatson: hi
[17:19] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:19] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:19] <cjwatson> ^- up to date with bug statuses
[17:19] <cjwatson> as per usual for this stage, most of our bugs are installation and upgrade bugs; I've gone through the High importance ones targeted to Lucid and milestoned a couple of those, too
[17:19] <cjwatson> most of the outstanding milestoned installer bugs continue to be Kubuntu issues, as ScottK just pointed out.  a recent new contributor helped to clear up quite a few of these so I think we'll make it, but it requires continued attention
[17:19] <cjwatson> thanks to slangasek for doing foundations-lucid-supportable-binaries, which accounted for most of our remaining work items :-)  I'm not worried about the rest
[17:19] <cjwatson> a few new lucid-targeted bugs have come up from oem-priority that we'll need to pay attention to over the next week in order to support future deployments of 10.04 LTS
[17:19] <cjwatson> that's all, folks
[17:20] <slangasek> no questions here; anyone else?
[17:21] <slangasek> [TOPIC] Security Team
[17:21] <MootBot> New Topic:  Security Team
[17:21] <slangasek> that was easy ;)
[17:21] <slangasek> cjwatson: thanks
[17:21] <slangasek> jdstrand: hi
[17:21] <jdstrand> hi!
[17:21] <jdstrand> so, as always: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:21] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:22] <jdstrand> all bps are done or postponed now
[17:22] <jdstrand> I followed up on bug #528274 this morning, but no progress afaics
[17:22] <jdstrand> from last week anyway
[17:23] <jdstrand> last week we talked about libvirt and you asked for me to mention its status
[17:23] <slangasek> I think I know the status now since there were 4 uploads of it into the freeze queue, but go ahead for the benefit of others ;)
[17:23] <jdstrand> we stuck with 0.7.5 as you recall. which the server team and I feel is a good decision
[17:23] <jdstrand> heh
[17:24] <jdstrand> I was able to backport my 0.7.7 work to 0.7.5. all but one item, but it as a decent workaround that has been in place since karmic
[17:25] <jdstrand> all the work has been upstreamed, and will be in 0.7.8, except for this one item which changed some internals and will be in the following release
[17:26] <jdstrand> other than that, the security team is bug fixing, going through lucid to make sure it is up to date with security patches and we will be doing install audits next week
[17:26] <jdstrand> only 2 of those libvirt uploads were mine by the way ;)
[17:26] <jdstrand> that is it from me
[17:27] <slangasek> thanks
[17:27] <slangasek> any questions for security?
[17:27] <slangasek> [TOPIC] MOTU
[17:27] <MootBot> New Topic:  MOTU
[17:27] <slangasek> ScottK: are we there yet?
[17:27] <ScottK> Hello
[17:28] <ScottK> NBS is still needing work.
[17:28] <ScottK> Needs a look from someone that understands Ruby stuff and someone who knows about Tex packages
[17:29] <ScottK> FTBFS numbers aren't great either.
[17:29] <slangasek> we seem to have a real mess still with tetex in particular; I had pinged the dev who requested the sync, but no answer
[17:29] <pitti> at this point it might be easier to reintroduce the transitional packages?
[17:29] <pitti> instead of trying to fix dozens
[17:29]  * ScottK has no opinion.
[17:30]  * ScottK just wants it resolved ....
[17:30] <slangasek> maybe, if you can reliably sort out how they're supposed to fit together - the tex packaging is a bit scary
[17:30] <pitti> I did some NBS stuff in the past days, but the ruby stuff didn't look trivial, so I ignored it admittedly
[17:30] <ScottK> Also there's some Ruby related stuff in New.  Not sure how much that will help NBS.
[17:30]  * ScottK doesn't know anyone but lucas that understands it.
[17:31] <ScottK> I've made some progress on Python stuff, but only stuff that FTBFS.  I didn't get as far as does stuff work.
[17:31] <ScottK> Anyone who could help look at recent Debian uploads would be appreciated.
[17:31] <ScottK> That's all I've got.
[17:32] <slangasek> look at recent Debian uploads> do you have a recommended workflow for that?
[17:33] <ScottK> No.  That's why I haven't done it.
[17:33] <ScottK> rcbugs page is probably a good start.
[17:33] <slangasek> ok
[17:34] <slangasek> ScottK: thanks
[17:34] <slangasek> [TOPIC] AOB
[17:34] <MootBot> New Topic:  AOB
[17:34] <slangasek> anything else?
[17:34] <ScottK> slangasek: We need to decide on timing for final freeze for Universe
[17:34] <ScottK> (not in the meeting, but soon)
[17:34] <ScottK> And get it announced.
[17:35] <slangasek> ScottK: I followed up to sistpoty's mail on ubuntu-release; 26 Apr seems fine to me as long as we're being judicious about not overloading the build queue
[17:35] <ScottK> OK.
[17:35] <ScottK> We can manage that as needed.
[17:36] <slangasek> if no one has any objections, I can include that date in a "freeze is coming" u-d-a mail today
[17:36] <ScottK> Given the recent rates of universe uploads, I don't expect it'll be a problem.
[17:36] <ScottK> Sounds good.
[17:37] <slangasek> one week to tax day^W^W final freeze, two weeks to RC, three weeks to release
[17:37] <slangasek> let's get out there and kick some bugs :)
[17:37] <slangasek> #endmeeting
[17:37] <MootBot> Meeting finished at 11:37.
[17:37] <pitti> thanks everyone
[17:38] <slangasek> thanks!