/srv/irclogs.ubuntu.com/2010/03/26/#ubuntu-meeting.txt

=== kamalm is now known as kamalm-away
=== doko__ is now known as doko
=== jamie is now known as Guest31141
=== zul is now known as sorensbot
=== sorensbot is now known as zul
=== kamalm-away is now known as kamalm
=== jsalisbury_ is now known as jsalisbury
pittio/16:01
* slangasek waves16:01
* marjo waves16:02
ScottKo/16:02
* ogasawara waves16:02
ttxo/16:02
slangasek#startmeeting16:02
MootBotMeeting started at 11:02. The chair is slangasek.16:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:02
slangasek[LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-2616:02
MootBotLINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-2616:02
ScottKpitti: I'll be giving the Kubuntu report today since Riddell is away.16:02
jdstrando/16:02
slangasek[TOPIC] Actions from previous meetings16:03
MootBotNew Topic:  Actions from previous meetings16:03
slangasek  * review status of branding for Kubuntu, Edubuntu next week16:03
slangasek  * asac to talk to mozilla upstream about the need for system cairo in Ubuntu16:03
asaco/16:03
slangasek  * ScottK, slangasek to review python sync/merge candidates16:03
slangasek  * pitti to get people to investigate #52852416:03
slangasek  * pitti to file bug about sound indicator being muted16:03
pittisorry, I'll be "really" here in a minute; firefox ate all my tabs16:03
pittislangasek: sound indicator bug filed, conor is debugging it16:03
slangasekScottK: any progress on branding?16:03
slangasekstgraber: ^^16:04
slangasekpitti: ok, great!16:04
ScottKslangasek: Nope.  Silence.16:04
slangasekasac: have you reached out to Mozilla upstream?16:04
pittiand #528524 made some progress16:04
slangasekScottK: mm16:04
asacslangasek: awaiting reponse from them today on the cairo bug. they want to pursue this upstream and have assigned a dev to it (so it gets finally resolved).. if we dont get anything by monday we will go with what we have and replace it when they have a real solution16:04
slangasek[ACTION] slangasek to shake the branding tree and see what falls out16:04
MootBotACTION received:  slangasek to shake the branding tree and see what falls out16:04
pittislangasek: wrt. mozilla, we decided to go ahead and apply the patch in the firefox source; Chris Coulson did that, but now it's looking worse than before, so investigations ongoing16:04
ScottKslangasek: We need to think about if this is something we'd really want to touch after beta 2, but having an Ubuntu splash on Kubuntu is going to make a lot of users not happy.16:04
slangasekasac: that's a reasonable timeline, thanks.  Is Mozilla aware of this Monday deadline?16:05
slangasekpitti: er, heh16:05
asacslangasek: yes, they are aware of the urgency16:05
asacpitti: interesting. was that local build?16:05
pittiyes16:05
asacok fine16:05
slangasekpitti: 528524 - ok, good; is there a further action item there?  Is Luke the correct assignee to carry it forward?16:06
pitti*nng*, firefox, start16:06
pittislangasek: it should probably be reassigned to crimsun, he's currently working on it16:07
slangasekdone16:07
slangasekScottK: yes, I really wouldn't like us to be changing this post-beta2, so I'll see what I can do to get things moving16:08
slangasekScottK: python sync/merge - I have time for that today if you do16:09
ScottKPossibly.16:09
* slangasek nods16:10
slangasek[TOPIC] QA Team16:10
MootBotNew Topic:  QA Team16:10
slangasekmarjo: hello16:10
marjo* Hardware testing16:10
marjohttp://people.canonical.com/~fader/hw-testing/current.html16:10
marjoNetbook:16:10
marjo   passed:  11 (79%) failed:   1 ( 7%) untested: 2 (14%)16:10
marjoLaptop:16:10
marjo   passed:  32 (100%)   failed:   0 (  0%)   untested: 0 (  0%)16:10
MootBotLINK received:  http://people.canonical.com/~fader/hw-testing/current.html16:10
marjoServer:16:10
marjo   passed:  63 (91%)   failed:   0 ( 0%)  untested: 6 ( 9%)16:10
marjoDesktop:16:10
marjo   passed:  13 (100%)   failed:   0 (  0%)   untested: 0 (  0%)16:10
marjoper asac's request:16:11
marjo* Beta 1 Outstanding Serious Bugs Status16:11
marjohttp://people.canonical.com/~marjomercado/isotestingbugs.html16:11
MootBotLINK received:  http://people.canonical.com/~marjomercado/isotestingbugs.html16:11
asachah16:11
marjoasac: better?16:11
cjwatsonmarjo: can we get an assignee column in that list?16:12
asaclooks nice.16:12
cjwatsonif we can, a variant would supersede some hacking work I've been doing16:12
marjocjwatson: will do, thx for feedback16:12
slangasekmarjo: looks nice - though it looks like bugs that were referenced more than once are repeated, would be nice to fix that :)16:12
marjocjwatson: ok, working w/ bdmurray on improvements for usability16:12
cjwatsonstill some weird dups in that list16:12
marjoslangasek: ditto re bdmurray's help16:12
cjwatsoncan we get bugs actively *off* that list without fixing them?  bug 527377 has been true forever16:13
ubottuLaunchpad bug 527377 in ubiquity "on resize mode i can't choose in which disk install to" [Undecided,Confirmed] https://launchpad.net/bugs/52737716:13
slangasekmarjo: anything we need to discuss re: the 8 machines not yet tested for hw testing?16:13
marjocjwatson: sure, we can consider that16:13
fader_slangasek: We're actively looking at all of them.  The two netbooks we can test with a USB installer so they're certain to get tested soon16:14
marjoslangasek: not really, they're basically on deck16:14
cjwatsonmind you, I can just dup that bug16:14
marjocjwatson: go for it!16:15
fader_The dead HP server is dependent on HP getting it fixed and back to us; the one that needs a serial dongle should be up by EOD today16:15
slangasekmarjo, fader_: ok.  also, in past cycles there's been hw that was not yet provisioned that as a result wasn't even listed as "untested" - is there anything like that pending this cycle?16:15
fader_slangasek: Yes, anything we don't physically have is not reflected in this report.  As I receive hardware I add it to the list16:15
marjoslangasek: i think that's the proper way, doesn't make sense to list "not yet provisioned"16:16
fader_+1, especially as we're never 100% certain when or even if we will get all the hardware that is targeted :/16:17
slangasekmarjo: if it's hardware that we have an obligation to get provisioned and certified before it's too late to change 10.04 to fix anything, I think we do need to have it on the radar16:17
slangasek(but I have no visibility into what hw we might have such obligations on...)16:17
marjoslangasek: agree, will consider16:17
marjoslangasek: yes, that needs to be considered in the reporting16:18
marjonext topic ok?16:18
slangasekmarjo: can I give you an action item to check on this?16:18
marjoslangasek: please do16:18
slangasek[ACTION] marjo to confirm whether there are committments to certify any hardware for 10.04 that's not yet provisioned16:19
MootBotACTION received:  marjo to confirm whether there are committments to certify any hardware for 10.04 that's not yet provisioned16:19
slangaseknext topic16:19
marjoLucid Quality (wrt Bugs) Status Report16:19
marjo34 days left and 322 bug tasks to fix16:19
marjoBarring no new work - we need to fix 9 bug tasks a day now16:19
marjoThe Canonical Desktop Team needs to deal with 21 bug tasks16:19
marjoChris Coulson is the most overtasked with 10 bug tasks16:19
marjoMartin Pitt is rockin' with 66 bug tasks fixed16:19
marjoYesterday's hero was Martin Pitt with 2 bug tasks fixed16:19
marjonot exactly 34 days, due to final freeze milestone16:20
ttxand the day before yesterday, the hero was Martin Pitt.16:20
pittiI talked with Chris about his'16:20
bdmurraythe day before yesterday was actually Dustin! ;-)16:20
pittihe said he has fixes for many of them already, and the firefox ones will be fixed in one go16:20
ttxhah!16:20
slangasek:-)16:21
pittiDustin and I have a permanent race on http://qa.ubuntu.com/reports/bug-fixing/lucid-fixes-report.html, yes :)16:21
ttxwe are trying to help him, he releases most of the team fixes.16:21
pitti(oh, on par again .. /me pedals harder)16:21
marjoSpecs Status16:21
marjohttp://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-2.html16:21
marjohttps://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-bugs-hwdb-querying16:21
marjoStatus: On track16:21
marjohttps://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-bugs-hwdb-querying16:21
marjoStatus: On track16:21
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-2.html16:21
marjoslangasek: Bug:530380: checkbox writes to .cache/checkbox/submission before submission completes16:22
marjoStatus: cr3 has submitted the merge request. Waiting for review by release team.16:22
marjothat's it folks16:22
marjothanks for all the feedback16:22
marjohope you find the reports useful to focus your work on quality!16:22
marjoslangasek: that's it from QA team16:22
slangasekok, thanks!16:23
slangasekany questions from anyone?16:23
slangasek[TOPIC] Server Team16:23
MootBotNew Topic:  Server Team16:23
slangasekttx: hi16:23
ttxo/16:23
ttxSo we are in good shape with beta2-targeted bugs, mostly thanks to a eucalyptus sprint where smoser, mathiaz and kirkland have been fixing the euca beta2-targeted issues16:24
ttxThe others should all get fixed by beta2Freeze16:24
ttxI'll mention bug 522509 being blocked by a FFe16:24
ubottuLaunchpad bug 522509 in tftp-hpa "[FFE] tftpd-hpa doesn't start on boot" [High,In progress] https://launchpad.net/bugs/52250916:24
=== yofel_ is now known as yofel
ttx... which might not be necessary (conversion to upstart is a feature ?)16:24
ttxAh, I forgot to paste the link16:25
ttxhttps://wiki.ubuntu.com/ServerTeam/ReleaseStatus16:25
ttxmakes it easier to follow ;)16:25
slangasek[LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus16:25
MootBotLINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus16:25
ttxQuestions about our beta2-targeted bugs ?16:25
slangasekwell, upstart jobs are all still supposed to be passed to Foundations for review prior to upload, so an FFe works as well as anything for that16:26
ttxslangasek: ok :)16:26
slangasekI can review this today16:26
ttxcool, thanks16:26
ttxOn the specs side, looking at High specs < 75 % completion:16:26
ttxserver-lucid-uec-testing (33% completion): Incompatibilities between testrig and installer capabilities threaten multi-network automated testing, in which case we'll switch to manual testing. The rest is on track.16:27
ttxserver-lucid-papercuts (33% completion): On track, one work item per week. 11 targets, 36% fixed16:27
ttxwill work next week on improving that score16:27
ttxserver-lucid-eucalyptus-merging-and-packaging (71% completion) is onn track16:27
ttxserver-lucid-ec2-ebsroot (0%): just a cleanup script is missing, should be completed by Tuesday16:27
ttxBugs affecting server, in other teams:16:28
ttxbug 531494: upstart does not run cloud-init job (Foundations)16:28
ubottuLaunchpad bug 531494 in upstart "cloud-init job sometimes not running in cloud images without ramdisk" [Critical,Confirmed] https://launchpad.net/bugs/53149416:28
slangasekttx: is mathiaz actively working on the openldap bugs?  I can easily see those overrunning the beta freeze if he doesn't get an early start on them16:28
ttxI couldn't get an updated status from him on those16:28
ttxI'll watch ethm and possibly help16:28
slangasekok16:29
ttxI've been discussing this bug with cjwatson16:29
padhuttx: great job of ubuntu team16:29
ttxsince foundations need to prioritize where they spend their upstart/plymouth efforts16:29
ttxwe have a way to trigger the bug much less often, which is the workaround we did for beta116:29
ttx(re-enable ramdisks)16:29
ttxso we'll reenable them for lucid. Doesn't mean the bug shouldn't get fixed16:30
ttxsince it's a race that can certainly still be lost16:30
ttxsome questions remains around the EC2 images16:30
slangasek"less often" - that hardly sounds like something we want to leave you with for release16:30
ttxsince they ship without ramdisk for quite some time in Lucid now16:30
ttxslangasek: taht was an overstatement16:31
ttxwe never lost the race so far with ramdisk enabled16:31
ttxbut we still fear the race could be lost.16:31
Keybukshouldn't get fixed => the problem is that the cause of the bug has not been isolated16:31
cjwatsonI don't think a fix is going to be practical at this point16:31
slangasekttx: ah, ok16:31
Keybukand it's impractical to expect foundations to isolate the causes of bugs that are only replicable on cloud systems16:31
Keybuk(since only server are familiar with them)16:31
ttxlet's say that needs some combined expertise. But I agree your efforts are better spent elsewhere right now16:32
Keybukthe problem is the length of the "right now"16:32
* slangasek nods16:32
ttxso we still need to decide what's best for EC2 image, before Beta2freeze ideally16:32
ttxbug 527208: EC2 kernel fails to boot in c1.xlarge (Kernel)16:33
ubottuLaunchpad bug 527208 in linux-ec2 "ec2 instance fails boot, no console output on c1.xlarge" [High,Confirmed] https://launchpad.net/bugs/52720816:33
KeybukI believe that, legally speaking, the age at which I will not have a million things clamoring for my attention is 65 in this country ;-)16:33
ttxcould we clone you ?16:33
Keybukttx: I have indicated that I would be amenable to this approach, yes ;-)16:33
ttxI didn't get an update from jjohansen on this one16:33
ttxit was in good shape last time he reported about it, so I wonder why it's still open16:34
slangasekogasawara: ^^ do you know where that bug sits?16:34
slangasek"in good shape" how?16:34
ttxThe others are well-known issues about installer16:34
ttx"slangasek: fix tested and working"16:34
slangasekok16:34
ttxbug 527401, bug 539324 and bug 54692916:34
ubottuLaunchpad bug 527401 in partman-base "grub-installer fails to install on a raid1 array" [High,Fix released] https://launchpad.net/bugs/52740116:35
ubottuLaunchpad bug 539324 in debian-installer "Setting up swap fails when setting lvm+encryption" [High,Confirmed] https://launchpad.net/bugs/53932416:35
ubottuLaunchpad bug 546929 in linux "most PATA/SATA modules missing in Lucid netboot" [Critical,Fix committed] https://launchpad.net/bugs/54692916:35
* JFo looks those over16:35
cjwatsonthe first one's done, you're out of date :)16:35
ttxbeh16:35
ttxOther/future issues expected to impact the Lucid release:16:35
cjwatsonsmb promised that the third would be uploaded today16:35
smbcjwatson, Yep working on that16:35
ogasawarattx, slangasek:  I'll get with jj when he gets back from vaca about it's current status16:35
ttxRising controversy from an otherwise-calm community about missing server boot messages16:35
ScottKThe opinions are pretty one sided on that.16:36
ttxI discussed it with cjwatson and I think we ahve an agreement that the default server boot should be more verbose16:36
ttxand not hide any init.d output16:36
ogasawarattx: 546929 should have a fix uploaded today16:36
slangasekttx: hum, plymouth doesn't give us many options there; we have one dip switch for "verbose", and that's to turn off splash16:36
slangasekanything else requires plymouth development work16:37
Keybukhuh16:37
ttxcjwatson mentioned other possibilities16:37
Keybukit gives you lots of options16:37
cjwatsonthere's a "details" plugin, I'm given to understand16:37
slangasekKeybuk: that don't require feature work?16:37
Keybukslangasek: indeed16:37
Keybukthe problem isn't Plymouth16:37
ttxwe have bug 542666, but it's about one side of the issues (suppressed init.d output)16:37
ubottuLaunchpad bug 542666 in upstart "No verbose output on ubuntu-server" [Undecided,New] https://launchpad.net/bugs/54266616:37
ttxnot really default behavior16:37
slangasekcjwatson: well, that gives *lots* of details (and is what happens when you disable 'splash')16:37
KeybukPlymouth has lots of features to capture console output and log them, and allow plugins to display them16:38
Keybukyou can even write graphical plugins with scrolling boot messages16:38
slangasekKeybuk: I'm including "plymouth theme work" in "plymouth development work"16:38
Keybukthe problem is that in Ubuntu, right now, we don't connect the init.d scripts to the console :p16:38
cjwatsonI don't think the server folk want anything graphical16:38
ttxcjwatson: I guess I need to file a better bug about "verbose text boot by default" ?16:38
Keybukslangasek: details behaves like this bu default16:38
Keybukcjwatson: Mark does AIUI16:38
Keybukthat being said16:38
cjwatsonKeybuk: so I've vaguely heard, but ttx didn't seem to know about this16:38
Keybukthose following bzr may have noticed that I've subtly arranged the packages so that server simply need to not seed a plymouth-theme-* package ;-)16:39
cjwatsonand if the server tech lead doesn't, I'm assuming that it has not been very clearly stated16:39
ttxand jib is with me, FWIW16:39
Keybukand then they'll have details.so only16:39
DavieyOne issue i've heard about is using Plymouth with a serial console, i haven't yet tried this.16:39
Keybukttx: if you and jib tell me not to seed a graphical theme ... I will not do so16:39
ttxKeybuk: works for me :)16:39
Keybuk(you have to tell me not to :p)16:40
ttxthat's about it from me16:40
slangasekalrighty16:40
slangasekany other questions for server?16:40
Keybukslangasek: just one note16:40
Keybukif the initramfs-tools update I just did works16:40
ttxcjwatson: should I file a bug about default text verbose boot for server ? If which, against which package ? plymouth ?16:40
Keybukthen I'm happy to re-enable "console output" for init.d scripts16:40
Keybuksince Plymouth will capture it all anyway16:41
slangasekshould it also be re-enabled for other upstart jobs?16:41
Keybukslangasek: the easiest thing will be just to change the default inside Upstart16:42
cjwatsonttx: file it on ubuntu-meta, subscribe me, and we'll take it from there16:42
ttxok16:42
slangasekKeybuk: easiest; but safe?16:42
cjwatsonsince we know we'll at least need a seed change16:42
Keybukslangasek: I can't think of any danger16:42
slangasekKeybuk: I can't either, but I think I'd like that change to happen before b2 freeze if it's going to so we have time to notice issues and back it out16:43
Keybukslangasek: *nods*16:43
KeybukI plan to have this plymouth package uploaded by three days ago16:43
slangasekexcellent, I'll test it yesterday16:43
slangasek[TOPIC] Mobile Team16:43
MootBotNew Topic:  Mobile Team16:43
slangasekasac: hi :)16:43
asachi16:43
asac[LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid16:44
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid16:44
asacso openoffice fix uploaded. somehow the build is still in queue16:44
asacso pending verification16:44
asacomap enablement is chunk of work now for rest of cycle16:44
asacit didnt went as well as hoped16:45
asacbut thats expected16:45
asackernel is broken, but seems on track to be fixed by amitk16:45
slangasekhum, the bug had said there was a successful build of OOo already, oops16:45
asacall i know is that we havent verified the latest upload on our own :)16:45
asacso omap being a bit behind made a late MIR for x-loader and uboot go away16:46
asacwe will rely on the flash being properly setup for omap this cycle16:46
slangasekasac: oh, there's a 3.2.0-4ubuntu2 upload as of 9h ago, with unrelated changes - is -4ubuntu1 tested at all?16:46
ograi think -4ubuntu1 was what doko was referring to in his comment16:46
asacslangasek: right. its not tested by our QA and i dont believe it until they confirm16:46
slangasek(is it still installable, or does the reupload break that?  if it's not installable, can I suggest grabbing the dependencies from the librarian by hand?)16:46
asac;)16:46
ograunless we want more testers that should be closed16:47
asacbut its probably fixed16:47
asacslangasek: we will get that verified today16:47
slangasekright - if there's enough doubt about the fix to be keeping the bug open, then you shouldn't be waiting until Monday for -4ubuntu2 to be built on arm16:47
asac*nod*16:48
ografor the omap image building we could need some help from a cdimage person, StevenK integrated my build scripts, we have livefses but somehow no actual image comes out on the rear end16:48
pittiI think it was closed, but doko reopened it again because debian/copyright was wrong or so16:48
ograi cant find any problem looking at the code16:48
pitti(doko tested it and said OO.o was working fine on arm now..)16:48
dokoogra: I checked that the notice is removed in 4ubuntu216:48
ogradoko, great, so it can be fully closed now16:49
slangasekogra, asac: I need to talk to someone about this omap stuff and what our expectations for release are, because this was never mentioned when https://wiki.ubuntu.com/LucidLynx/ReleaseManifest was being put together and I expect anything we do there for 10.04 to land *very* rough16:49
asacslangasek: yes, sory for that16:49
asacslangasek: we can go over that on monday16:49
slangasek[ACTION] slangasek, asac to discuss omap plans for 10.0416:50
MootBotACTION received:  slangasek, asac to discuss omap plans for 10.0416:50
ograslangasek, we dont do any special effort, userspace works as well as on other armel, the only issues are kernel related for 10.04 there is a "as good as it gets" approach16:50
slangasekogra: yes, I want things pinned down a bit more specifically then that; will discuss with asac on Monday as suggested16:51
asacso on spec front only thing that is missing is email webservices, where i waited for permission to use icons of the mail providers ... i think this wont happen, so i am redoing bits of the integration to work well without icons. that will go up asap then we are set16:51
slangasekasac: you have bug #532733 on your list, which is marked 'medium' - bump to 'high'?16:52
ubottuLaunchpad bug 532733 in qemu-kvm "apt/dpkg in qemu-system-arm hangs if a big task is installed" [Medium,Confirmed] https://launchpad.net/bugs/53273316:52
asacslangasek: yes, we can make that high16:53
ograhigs seems appropriate ...16:53
asacwe have no lead on that though16:53
slangasek<shrug> you've marked it as a blocker and said it should be RC, so 'high'16:53
asacyes16:53
asacdone16:53
slangasekanything else?16:54
asacthe few thumb2 porting bugs will get resolved before beta-216:54
=== zul_ is now known as zul
asaceither by getting the real fix or by dropping to -marm ...16:54
asacits two that have no fix according to my book16:54
* slangasek nods16:55
asacbesides from that we are done16:55
slangasekany questions for mobile?16:55
slangasek[TOPIC] Kernel Team16:56
MootBotNew Topic:  Kernel Team16:56
asacthanks ;)16:56
ogasawaraOverall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Beta-2 activity is summarised at the second URL below, with items pushed out shown as At Risk.  The burndown chart for Beta-2 is at the third URL, and our burndown chart is at the fourth:16:56
ogasawara    [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid16:56
ogasawara    [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-216:56
ogasawara    [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team-ubuntu-10.04-beta-2.html16:56
ogasawara    [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg16:56
slangasekasac: thank you!16:56
ogasawaraOf the pushed out Beta-1 items, the investigative tasks are either complete or on track to be complete by beta-2.  The remaining items should be nearing completion with patches awaiting final review, test, and upload.16:56
ogasawaraOn the items pulled out on the agenda, our blueprint status is as follows:16:56
ogasawara  * The KMS strategy review has one bug In Progress with test kernels built and posted.  The other bug is still under investigation.  The remaining work item is investigative and should be on track to complete by beta 2.16:56
ogasawara  * The ureadahead optimisation work remains to be tested but is a small patch kernel side and does not impact any features.16:56
ogasawara  * Apparmor development saw another push to LKML this week and is still hoping to hit the 2.6.34 release.16:56
ogasawara  * The configuration review is complete and patches to pull out some built-in drivers have been committed and released.16:56
ogasawara  * For bug handling, the documentation review is now complete and a re-work of the kernel team wiki's is underway.16:56
ogasawara  * The investigation of ALSA quirks which could likely leverage the device tree work has been postponed to M.16:56
ogasawaraOur list of bugs on the agenda grew quite substantially this week compared to last.  I've posted a status summary for each bug on our release status page, https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid .  Patches and/or test kernels have been posted for the majority.  Bug 491210 doesn't seem to have been confirmed to exist with Lucid so I'm questioning if this should really be milestoned for beta-2 at the moment.16:57
ogasawara  I also assigned bug 544741 to our team to get futher investigation.  I'll get with apw asap when he returns to try to get kernels uploaded with fixes for the majority and avoid having to SRU these.  An upload should be happening today to close out bug 546929.16:57
ubottuLaunchpad bug 491210 in linux "[i865G] Monitor Resolution limited to 800x600" [High,Confirmed] https://launchpad.net/bugs/49121016:57
ubottuLaunchpad bug 544741 in linux "[X700] KMS, amd64: Kernel panic while trying to launch system > preferences > appearance" [High,Triaged] https://launchpad.net/bugs/54474116:57
ubottuLaunchpad bug 546929 in linux "most PATA/SATA modules missing in Lucid netboot" [Critical,Fix committed] https://launchpad.net/bugs/54692916:57
ogasawaraAlso, linux-2.6.32-17.26 was uploaded last week and primarily contains the 2.6.32.10 stable patches. linux-fsl-imx51-2.6.31-605.10 was also uploaded last week and contains a fix for bug 537083. The new linux-ti-omap-2.6.33-500.3 also landed yesterday which should provide us a reference kernel for the TI OMAP ARM processor.16:58
ubottuLaunchpad bug 537083 in linux-fsl-imx51 "Suspend no longer works after updating to 2.6.31-605.9 kernel" [High,Fix released] https://launchpad.net/bugs/53708316:58
ogasawara<done>16:58
slangasekogasawara: "patches to pull out some built-in drivers" - do you mean that there are still some changes there that are committed but /not/ released, or have they all been released?17:00
ogasawaraslangasek: should all have been released17:00
slangasekok, because I'd have to nack any further reshuffling of the kernel config on that level, given the critical bug we already have regarding sata drivers missing from netboot17:00
ogasawaraslangasek: ack, the netboot bug was a result of that shuffling17:01
slangasekyes :)17:01
ogasawaraslangasek: smb should be uploading that fix today17:01
cjwatsonnetboot> and everything else17:01
cjwatson(notwithstanding the bug title)17:02
slangasekScottK: looks like you've volunteered to test bug #491210?17:02
ubottuLaunchpad bug 491210 in linux "[i865G] Monitor Resolution limited to 800x600" [High,Confirmed] https://launchpad.net/bugs/49121017:02
ScottKslangasek: Yes, but didn't get to it yet.17:02
slangasekScottK: think you will by Monday?17:03
ScottKMaybe.17:03
ScottKNeed to either find my USB stick or my stack of CDRs.17:03
slangasek357673 is an action item from me, to test the kernel patch that implements the alsa mixer for the thinkpad bios17:03
slangasekI'll get that done today17:03
slangasekScottK: ack :)17:04
slangasekany other questions for kernel?17:04
slangasek[TOPIC] Desktop Team17:04
MootBotNew Topic:  Desktop Team17:04
slangasekogasawara: thanks17:04
pitti[LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus17:04
MootBotLINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus17:04
pittibeta-2 WIs are well on track (7 left to do), we are in almost 100% bug fixing mode now17:04
pittiGood progress with RC and general bug fixing, but they keep coming in. (Which is actually an improvement in processes and cooperation with QA, thanks to them! At least we know very well where the fires are)17:04
pittiSpecs called out in release team meeting invitation:17:05
pitti- desktop-lucid-xorg-multitouch: Code changes for Lucid are done. One remaining WI is testing, the other is evaluating kernel changes, which I believe was just forgotten to be closed. Will check with Andy when he comes back next week.17:05
pitti- desktop-lucid-startup-speed: Only WI left is for OLS team, to defer startup of u1 sync daemon; being worked on, and trivial to fix17:05
pitti- lucid-duplicated-packages: Dropping db4.7 still seems feasible to do; we probably have to defer tcl/tk8.4 at this point of the release cycle.17:05
pittiBugs called out in release team meeting invitation:17:05
pitti- bug 537356 - that is for the mobile team17:05
ubottuLaunchpad bug 537356 in webservice-office-zoho "application menu entries dont do anything" [High,Triaged] https://launchpad.net/bugs/53735617:05
marjopitti: thank you!17:05
pitti- as a fair trade, bug 432631 is in the desktop field now (from foundations)17:05
ubottuLaunchpad bug 432631 in sudo "clean up system/per-user proxy handling" [Medium,In progress] https://launchpad.net/bugs/43263117:05
pittistatus for other bugs is on the wiki page, I spare the copy&paste17:06
pittiI also have three questions to discuss, shall I go ahead with them?17:06
cjwatsonthat's a fair trade as far as I'm concerned!17:06
* slangasek grins17:06
slangasekpitti: yes, go ahead17:06
pittiLast week, after releasing beta-1 with an one-day delay, we thawed very late (after Europe went to sleep and weekend already); that caused some interesting fallout over the weekend. For situations like that, can we either thaw earlier (when it's clear that we won't rebuild any more), or defer the thawing until the Monday after?17:06
cjwatsonmy opinion at the time was that it wasn't clear that we'd have responded to the situation any more quickly on a Monday night than on a Friday night17:07
* pitti apologizes for the cdbs trouble17:07
cjwatsonI think it's worth examining the timeline in detail before responding17:07
pittiwell, there were some brave souls (thanks StevenK, persia) who worked on Saturday to fix it17:07
cjwatsonI think there are other things we should have done - there's no evidence that escalation was done to the extent of phoning people and getting them out of bed17:07
cjwatsonAFAICS17:08
pittiso in this particular case it wasn't too bad17:08
pitticjwatson: no, there wasn't17:08
slangasekpitti: I don't think it was practical to thaw earlier because the people who would do the thawing were still bound up in releasing17:08
pittiit's just a general strawman proposal to mitigate the impact17:08
slangasekwe could have unfrozen the archive for new uploads but left the queue in place for later review?17:08
cjwatsonI'd have been concerned about momentum problems with thawing later17:08
slangasekOTOH, I reviewed and accepted that cdbs upload thinking it looked reasonable in scope17:09
pittislangasek: that might be a good compromise17:09
cjwatsonsome of the very same people who were saying we should have thawed on Monday were clamouring for a thaw on Friday :-)17:09
robbiewcjwatson:FWIW, I was phoned...but could only update the twitter status :/17:09
ScottKslangasek: I think a better idea is people shouldn't upload stuff during the freeze they don't want in before the milestone.17:09
pitticjwatson: I suppose you mean seb128?17:09
cjwatsonrobbiew: were you out of your normal environment?17:09
cjwatsonpitti: I don't recall the names, and am not sure that naming names would be productive even if I did :)17:09
pittiTo be fair his concern was thawing on a Friday night, not thawing ASAP so that we can continue to develop lucid17:09
robbiewcjwatson: yes...and by the time I returned...folks were working on it17:10
slangasekScottK: desktop team wouldn't be happy with that, their workflow involves pushing things off their desk and into the queue ASAP17:10
cjwatsonrobbiew: ah17:10
pittianyway, no need to spend a long time discussing this, but I thought I'd bring it up17:10
pittislangasek: well, we do that because it's possible17:11
cjwatsonpitti: when it wasn't possible, there were many objections17:11
slangasekpitti: and if it wasn't possible, seb128 wouldn't be happy :-)17:11
pittiif it's better to not stash uploads that way, we can stop doing that17:11
pittiwe have bzr, after all17:11
cjwatsonI think it's fine to stash uploads that way, personally, but I think we could have responded better to the situation that arose17:11
cjwatsonthere was some explicit handoff that wasn't done, too17:12
pittiI guess it also comes down to "test your changes better" (which I take as a "brown paperbag" for me)17:12
cjwatsonit wasn't really perceived as a crisis until it was far too late, AFAICS17:12
ScottKI know I initially was confused because the problem description sounded to me a lot like what the upload was intended to fix.  My initial thought was it was people who hadn't updated with problems.17:12
pittiok, thanks everyone for your opinions17:14
pittiI guess I should go on17:14
pittiFFE bug 546933 -- should we go ahead with this? It looks like a quite intrusive change, but it'd avoid releasing a third configuration format change for input devices, and also get us much better aligned with Debian; and it's also relatively easy to test; but like any change of that magnitude, there's a certain regression potential, of course17:14
ubottuLaunchpad bug 546933 in xorg-server "FFE: xorg.conf.d/inputclass backport" [Wishlist,Fix committed] https://launchpad.net/bugs/54693317:14
pittishould we disuss that in the meeting, or in the bug report?17:14
slangasekbug report, I think17:14
pittiok17:15
pitti</report>17:15
ScottKFor Kubuntu:17:15
ScottKWe expect KDE 4.4.2 tarballs to start packaging any moment now, so that should be our version for Beta 2 and almost certainly for release.  Likely we would upload this Monday or Tuesday.17:15
ScottKBranding has already been discussed.17:15
ScottKtseliot's Plymouth smooth transition patch for KDM is uploaded.  kdebase-workspace is building now.17:15
ScottKThat's all I have.17:15
slangasekany other questions for desktop team?17:15
slangasek[TOPIC] DX Team17:16
MootBotNew Topic:  DX Team17:16
slangasekpitti, ScottK: thanks17:16
slangasekdavidbarth: hi17:16
=== nikolam is now known as Guest57625
slangaseknjpatel_: around?17:18
slangasekok, moving on; we'll circle around if they show up later17:18
slangasek[TOPIC] Foundations Team17:18
MootBotNew Topic:  Foundations Team17:18
slangasekcjwatson: hi17:18
cjwatson[LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid17:19
cjwatsonRelease collaboration with Debian: per doko, we currently have a pre-release of IcedTea 1.8 in lucid, and both lucid and squeeze will get 1.8 final (no new features) in time for lucid release17:19
MootBotLINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid17:19
cjwatsonWe are pretty much in full bug mode now; see the URL above for status of trailing work items.  slangasek, what's happening with foundations-lucid-supportable-binaries?17:19
cjwatsonThere are still quite a few installer bugs (Steve expressed concern about this in the agenda), but we fixed three milestoned ones today and are making good parallel progress on several more.  The worst outstanding one is the LVM+encryption failure, which I'm working on.17:19
cjwatsonFor full bug details, see the URL above.17:19
cjwatson(that's it, short summary, long wiki)17:20
slangasekcjwatson: supportable-binaries> I'm going to plow through this today/tomorrow17:20
njpatel_slangasek, hey17:20
slangaseknjpatel_: hi; are you available to give us a DX status update after we finish w/ Foundations?17:21
davidbarthslangasek: sorry, currently on a call; the weekly report is at the usual location: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus#preview17:21
cjwatsonslangasek: can I help?17:21
njpatel_erm, let me see, I though dbarth was around for todays (I don't know the status of the blueprints)17:21
cjwatsonmind you maybe I should be fixing my bugs instead17:21
slangasekcjwatson: yeah, I think having two people working on this is probably a waste, I just need to sit down and finish it17:22
slangasekunfortunately it went long enough after UDS without action that the memories faded a bit, and the spec doesn't fully document the agreed algorithm for identifying removal candidatse17:23
ScottKslangasek: We can discuss that if you want.17:23
=== nikolam_ is now known as nikolam
ScottK(later)17:23
slangasekScottK: sounds good17:23
slangasekno more questions from me on Foundations; anyone else?17:24
cjwatsonthe second beta has been good in that it's given us time to shake out a bunch of serious installer bugs, but it's been bad in that the bug flow has been enormous.17:24
cjwatsonwe should post-mortem at UDS17:25
* slangasek nods17:25
pittihowever, we get a lot of "good" bug reports due to that, too17:25
marjocjwatson: agree, but i think it's a good thing overall17:25
cjwatsonpitti: we do, it's a mix17:25
pittimix> absolutely17:25
slangasekpost-mortem> we're not dead yet, let's save this conversation for UDS :)17:25
cjwatsonhe's pushing up the daisies!17:25
marjoslangasek: agree17:26
cjwatsonhe's gone to join the choir invisible17:26
cjwatsonahem17:26
slangasek[TOPIC] DX Team17:26
MootBotNew Topic:  DX Team17:26
slangasek[LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus17:26
MootBotLINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus17:26
Keybukslangasek: easy for you to say17:26
slangasekany questions for DX?17:26
slangasekdavidbarth, njpatel_: there were a couple of WIs on dx-lucid-me-menu that were still targeted to beta-1 which I've moved; it's ok if you don't have status on those currently, but I want to make sure it's on your radar17:28
njpatel_slangasek, thanks, will take a look through the blueprints again17:28
slangasekKeybuk: if you're dead, don't admit it, that'll just tell people you don't need to take breaks for physical needs ;)17:29
slangasek[TOPIC] Security Team17:29
MootBotNew Topic:  Security Team17:29
slangasekjdstrand: hi17:29
jdstrandhi17:29
jdstrandhttps://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid17:30
slangasek[LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid17:30
MootBotLINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid17:30
jdstrandnot a lot to report (again). we are in bug fixing mode. one bug worth mentioning is bug #52827417:30
ubottuLaunchpad bug 528274 in ubuntuone-client "syncdaemon should have AppArmor profile" [High,Fix committed] https://launchpad.net/bugs/52827417:30
jdstrandit has been unmilestoned and deferred to lucid+1 due to all the changes with ubuntu-one that are still landing (ie, profiling a moving target is difficult). I suggested that we at least ship a supported but disabled profile, like we do with firefox, which we can turn on in 'm'. It seems the ubuntu-one people will do this.17:30
slangasekok17:31
slangasekany questions for security? :)17:31
jdstrandnone from me ;)17:32
slangasek[TOPIC] MOTU17:32
MootBotNew Topic:  MOTU17:32
slangasekjdstrand: thanks17:32
jdstrandsure! :)17:32
slangaseksistpoty|work, ScottK: how goes?17:32
sistpoty|worko/17:33
* ScottK lets sistpoty|work go first.17:33
sistpoty|workslangasek: didn't have much time for ubuntu this week, so nothing to report from my side :(17:33
ScottKThere was some concern about the pace of syncs for the Ruby transition this week.17:33
ScottKThat got into a long discussion about how we deal with syncs in general.17:34
ScottKI found out today that due to the fix for http://bugs.python.org/issue691291 landing in the archive in python2.6.5, we broke at least one package.17:34
ScottKFortunately the Debian maintainer had already fixed it and I got it sync'ed.17:34
ScottKI don't know how many others (if any) got broken.17:35
ScottKBug #548849 is the one in question.17:35
ubottuLaunchpad bug 548849 in gaupol "Sync gaupol 0.15.1-1 (universe) from Debian unstable (main)" [Wishlist,Fix released] https://launchpad.net/bugs/54884917:35
ScottKDo we have a good way to investigate this?17:35
ScottKBTW, thanks jdstrand for the sync.17:36
ScottKThat's all I have.17:36
slangasekdoko: ^^ do you have any insight here?17:36
cjwatsonis there a way to grep for the problem?17:36
dokolooking17:37
cjwatsonwe don't have an unpacked lintian lab like Debian, but we could do a full-source grep, it would just take a while ...17:37
ScottKcodecs.open( ... would give you a list.17:37
cjwatsonwhat was the breakage?17:37
ScottKIt wouldn't be all that use the function, just those that made the wrong assumption about binary/text mode.17:37
cjwatsonah17:38
jdstrandScottK: you're welcome17:38
dokohmm, have to run, will look at this tomorrow ...17:38
ScottKslangasek: Maybe an action then.17:38
slangasekdoko: you're taking that action?17:39
slangasek[ACTION] doko to grep the archive for codecs.open in python code, to find other packages broken by http://bugs.python.org/issue69129117:39
MootBotACTION received:  doko to grep the archive for codecs.open in python code, to find other packages broken by http://bugs.python.org/issue69129117:40
slangasekanything else?17:40
sistpoty|workoh, we've got delegates still outstanding17:40
ScottKWe seem to be doing OK without ....17:40
sistpoty|work*shrug*17:41
slangasekI keep promising to reply to that email and it hasn't happened17:41
slangasekI'm afraid part of it is I keep winding up bogged down trying to map nicknames in the mail to people17:42
slangasekand then I get pulled away17:42
slangasekI'll reply today for reals17:42
sistpoty|workthanks!17:42
sistpoty|workslangasek: if you want, I can resend with a list of lp-ids and names instead of only nicks17:43
slangaseksistpoty|work: if you can do that quickly, that would certainly expedite my response :)17:43
slangasek[TOPIC] AOB17:43
MootBotNew Topic:  AOB17:43
davidbarthslangasek: it is, there's no remaining feature to implement; mostly a reminder to check for IM client status bugs (sorry to talk on another topic)17:43
slangasekdavidbarth: ok17:44
slangasekgoing once...17:44
slangasekgoing twice...17:44
slangasek#endmeeting17:44
MootBotMeeting finished at 12:44.17:44
slangasekthanks, folks17:44
marjoslangasek: thx17:44
pittithanks everyone17:46
sistpoty|workslangasek: sent17:58
slangasekthanks!17:58
=== txwikinger2 is now known as txwikinger
=== txwikinger is now known as txwikinger2
=== txwikinger2 is now known as txwikinger

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!