/srv/irclogs.ubuntu.com/2010/02/23/#ubuntu-meeting.txt

=== mhall119|SCaLE8x is now known as mhall119|work
=== nhandler_ is now known as nhandler
=== ikt_ is now known as ikt
lifelessStevenK: do you stillhave my mini usb adapter?09:46
lifelessmini-ide--usb that is09:46
StevenKThat's an awfully good question ...09:50
StevenKI thought I returned it09:50
lifelessDid I give you the plastic cover, or jsut the guts?09:51
lifelessreason I ask, isn't because I need it back - I don't atm09:51
lifelessbut because i'm tifying up, if I just gave you the guts and I find a plastic outer, I'll know what to do with it :)09:51
StevenKYou gave me the plastic cover and the guts09:55
lifelessok cool09:56
TheMusoamachu: Hi10:04
persiaOh, it's a fourth week, isn't it.10:06
lifelessyah10:07
persiaSo we just need freeflying amachu and elky ?10:10
lifelessthat would give us 610:10
lifelesswhat is quora10:10
persiaWe've been operating on 410:10
persiaSo any one of them.10:10
* persia has no idea as to the actual determinants or rules, and is loosely guided by the "everyone has veto except when they don't" model10:11
lifelessonly vish is here10:12
lifelesselky: ping10:12
lifelessfreeflying: ping10:12
lifelessamachu: ping10:12
persiaDoes the string "ping" actually do anything in te default configurations of any clients?10:13
lifelessannoys people10:13
lifelessI don't know of a client where it does something special10:13
persiaWell, sure, but how is it different from hilighting in other ways?10:13
persiaWell, I've seen plugins where it automatically gets rejected, sometimes with a contentless-pong response.10:14
lifelesspersia: its not10:14
lifelesspersia: the main thing was <nick>: which is all some clients highlight on10:14
persiaAh.10:14
TheMusoso...10:26
freeflyinglifeless: pong10:26
freeflyinglifeless: sorry, for late10:27
persialifeless: You remembered about it: you're chair :)10:27
lifelesspersia: amachu emailed us10:27
lifelessvish: are you there?10:27
vishhi.10:27
lifelesspersia: do you know how to drive mootbot ?10:28
lifelessvish: tell us about yourself and your contributions to Ubuntu10:28
vishHi.. I'm Vishnoo from Chennai , India. I mainly do artwork , mockups for Ubuntu projects and Triage bug reports in launchpad.10:28
persialifeless: You start with "startmeeting" proceeded by '#'10:29
persiaAnd it gives you instructions in /query10:29
lifeless#startmeeting10:29
MootBotMeeting started at 04:29. The chair is lifeless.10:29
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]10:29
vishA list of the Ubuntu projects for which I'v made contributions are listed in the wiki page. https://wiki.ubuntu.com/vish10:30
vishInitially, when I started contributing , it more because I was surprised that Ubuntu OS was a community project, and wondered if i could _really_ help make a difference to an OS.10:30
vishAs i got more involved , I got more familiar with the projects ,people and noticed that my contributions were warmly welcomed , appreciated and encouraged.10:30
vishI started contributing more.10:31
vishAnd nowadays I spend a few hours of my day working on Ubuntu projects10:31
lifelesspersia: freeflying: TheMuso: I've got enough; if you have questions for vish please ask away.10:31
lifelessback in a sec, grabbing more water10:32
amachuback10:32
* persia is very familiar with vish, and has no specific questions10:32
amachugot out on a important issue10:32
persiaHrm, actually, I do have a question.10:34
persiavish: Why did you not ask for people to support you in this meeting in some of the IRC channels and mailing lists in which you are most active?10:34
lifelessamachu: no worries, we're doing the do10:34
persia(or even announce your membership intent)10:34
lifelesspersia: looks like vish got testamonials organised for the meeting - today even10:35
sagaciis this a membership interview or a public meeting10:35
lifelesssagaci: yes10:35
vishpersia: oh.. I never knew the memberships need to be announced on mailing lists. I told the people who were most aware of my work to submit testimonials , since I wasnt sure of the timings10:36
persiavish: Fair enough.  I just didn't see anything about it, but it seems to have worked for you.10:37
lifelessvish: they don't :P10:37
persiaThere's certainly no protocol, but often there's public requests for help in some forum.10:37
lifelessfreeflying: TheMuso: any comments/questions?10:37
TheMusonot from me.10:38
lifelessfreeflying: if you don't have questions shortly I'll suggest we move to voting10:39
freeflyinglifeless: no10:44
lifelessso, votes10:44
lifeless+1 from me10:44
TheMuso+1 from me also.10:45
persia+1 : great work.  membership is long overdue.10:45
* persia points out that the nifty [VOTE] feature could be used.10:46
lifelesspersia: you had the chance to organise :P10:46
lifelessso #stopmeeting10:47
persiaend10:47
lifeless#stopmeeting10:47
lifeless#end10:47
lifeless#endmeeting10:47
MootBotMeeting finished at 04:47.10:47
persiaBut we're looking for another vote.10:47
lifeless#needsabetterUI10:47
persiaYes :)10:47
amachu+1 vish10:47
lifelessamachu: will you do the group adding and notification ?10:48
amachuya ya10:48
amachulifeless: sure10:48
lifelesssweet10:48
vishthanks all.. :)10:48
lifelessvish: congrats10:48
hyperaircongrats vish =)10:49
persiavish: Welcome!10:49
vishthank you :)10:49
=== nhandler_ is now known as nhandler
vishpersia: usually how many days does it take to reflect new Ubuntu membership on user's lp teams?12:56
persiaZero to one.12:56
persiaYou're just waiting on amachu to organise things.12:57
vishah , ok.. thanks..12:57
persiaIs there something urgent that needs it done *now*?12:57
vishpersia: nah , just curiosity ;)12:57
persiaThe entire process of getting membership and all the cascade things usually takes a week or so.12:58
persiaAnd then you have to go through all the voluntary steps (like arranging and ordering your cards, etc.)12:58
persiaThat's usually another week.12:58
vishyeah..12:58
persiaBut there's another meeting about to start.  If you want to discuss more, please /query12:58
* ogra waves12:59
asaco/12:59
* StevenK shores13:01
* GrueMaster nods13:01
asacok guess ncommander isnt here ;)13:02
asaclets wait another minute or so13:02
ograyeah13:02
asactheni will take the meeting13:02
StevenKWhere will you take it too?13:03
ograto the END !13:03
asac#endmeeting :-P13:03
ograheh13:03
asacplars: persia: dyfet: ping13:04
asac(persia seems to be here)13:04
plarshello :)13:04
ograplars too :)13:04
asacdmart: also here?13:04
asaccooloney: ericm?13:04
dmartYeah, hi there13:04
asaccool. almost complete ;)13:04
* cooloney waves to asac 13:04
asac#startmeeting13:05
cooloneyeric is in Beijing for business trip.13:05
MootBotMeeting started at 07:05. The chair is asac.13:05
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:05
asac[LINK] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010022313:05
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010022313:05
asac[TOPIC] Action Items from February 16th, 201013:05
MootBotNew Topic:  Action Items from February 16th, 201013:05
asac*  * asac to arrange the next thumb2 team sprint. * asac to blog about the ARM alpha-3 release. * asac and JamieBennett to discuss the web office spec and come up with a way of moving it forward. * NCommander to link power management spec to dove bugs * GrueMaster to produce a daily report on image testing and add that to the weekly meeting page. * ogra to produce a rootstock test plan.13:06
asac * NCmmander to in vestigate KDE FTBFS issues. * Team to add individual summaries to standing items before meetings.13:06
asacooops ;)13:06
asac * asac to arrange the next thumb2 team sprint.13:06
ograhttps://wiki.ubuntu.com/ARM/RootstockTestplan13:06
asac * asac to blog about the ARM alpha-3 release.13:06
asac * asac and JamieBennett to discuss the web office spec and come up with a way of moving it forward.13:06
* persia rushes to try to complete the last of those quick-like13:06
asac * NCommander to link power management spec to dove bugs13:06
asac * GrueMaster to produce a daily report on image testing and add that to the weekly meeting page.13:06
asac * ogra to produce a rootstock test plan.13:06
asac * NCommander to investigate KDE FTBFS issues.13:06
asac * Team to add individual summaries to standing items before meetings.13:06
asacok ... so thumb2 team sprint13:06
asaci wanted to get a confirm of time before sending out mail to mobile ... 1100 UTC is what i have13:07
asacon Thu13:07
asacdoes that match what we discussed?13:07
persiaYes, although we were going to do it last week :)13:07
asacno13:07
ograyeah13:07
ogramatches13:07
dyfetyep13:07
asacok i will send the reminder out right after13:08
asac[ACTION] asac to blog about the ARM alpha-3 release.13:08
MootBotACTION received:  asac to blog about the ARM alpha-3 release.13:08
asacthis week is a313:08
asacso that matches13:08
asac* asac and JamieBennett to discuss the web office spec and come up with a way of moving it forward.13:08
ografriday is blogging day then :)13:08
asac-> we discussed this and found a good compromise using zoho viewer api13:08
asacstay tuned13:08
asac* NCommander to link power management spec to dove bugs13:09
asac-> did this happen, ogra?13:09
* NCommander kills his laptop13:09
asachi NCommander13:09
* ogra checks13:09
NCommanderhey asac, sorry for being late13:09
asacno problem ;) ... now i am the lead ;)13:09
NCommanderneeds a c/o13:09
* StevenK waits for -!- NCommander has quit [Ping timeout]13:09
asacStevenK: done13:09
ograNCommander, did you add the dove PM bugs to https://blueprints.edge.launchpad.net/ubuntu/+spec/mobile-lucid-arm-per-soc-powermanagement ?13:09
ograi dont see them there13:09
NCommanderogra: no, it needs a c/o13:09
ogra(and didnt get a notification)13:10
asac[ACTION] NCommander to link power management spec to dove bugs13:10
MootBotACTION received:  NCommander to link power management spec to dove bugs13:10
ograNCommander, do it now, its three clicks ;)13:10
asac* GrueMaster to produce a daily report on image testing and add that to the weekly meeting page.13:10
asac?13:10
GrueMasterC/o13:10
* asac carries that over13:10
asaccan we get that for next week?13:10
asac[ACTION] GrueMaster to produce a daily report on image testing and add that to the weekly meeting page13:11
MootBotACTION received:  GrueMaster to produce a daily report on image testing and add that to the weekly meeting page13:11
asac* ogra to produce a rootstock test plan.13:11
asac-> seems to be done13:11
ograhttps://wiki.ubuntu.com/ARM/RootstockTestplan13:11
asac14:06 < ogra> https://wiki.ubuntu.com/ARM/RootstockTestplan13:11
asacright13:11
ograpromoted to plars and GrueMaster last night13:11
asac* NCommander to investigate KDE FTBFS issues.13:11
asacNCommander: any progress on kde?13:11
NCommanderasac: its a segfault in kdebindings, but I haven't managed to run it down due to lack of time last week13:11
asacok ... makes sense to keep it on your list?13:12
ograasac, there are more urgent FTBFS since beginning of the week13:12
persiaNCommander: Riddell specifically asked that it be sorted soon, or smoke disabled for armel in the run up to alpha 3.13:12
ogra(which i asked NCommander to look at with help from dyfet )13:12
persiaNCommander: Needs to be today for a decision because of the freeze.13:12
ograwe need these to be fixed for A313:12
ograthey are all apps that are on the images13:12
asacso basically today13:12
NCommanderprobably best to disable smoke for kdebindings then13:13
ograthats why i asked NCommander early :)13:13
asacogra: whats the package list blocking a3 atm?13:13
ograbut i still see all of them13:13
asacevince i guess13:13
persiaNCommander: Please do that then :)13:13
asaceog13:13
asacwow13:13
ograasac, keyring and two indicators are FTBFS13:13
ograbeyond that gtk is our of sync but should be fine soon13:13
ogra*out13:13
asaceog is an out of synx thing13:13
persiaI looked at a lot of these earlier: most of them are failed detections of gtk+2.0 depwait13:14
ograyeah13:14
asacogra: ok. are the gtk bits there? maybe just give back13:14
persiasquid is the big one, but zul is on it.13:14
ograright13:14
persia(with help from lool)13:14
asacogra: gtk failed to build13:14
ograkeyring and the two indicators are the issues13:14
asachttps://launchpad.net/ubuntu/+source/gtk+2.0/2.19.5-1ubuntu5/+build/1526418/+files/buildlog_ubuntu-lucid-armel.gtk+2.0_2.19.5-1ubuntu5_FAILEDTOBUILD.txt.gz13:14
asacso top prio is gtk13:14
ograindeed13:14
asacseg fault13:14
asactry again13:14
ograthough there was just an upload 1/2h ago13:14
asacreally?13:14
* asac goes and kicks seb13:15
ograubuntu613:15
ograits bratches fault :)13:15
persiaseb128 seems to be all over the gtk stuff, in good ways.13:15
ogra*bratsche13:15
asacdone13:15
ograseb is only uploading13:15
asacright. seb could hold it back next time13:15
persiaWell, and paying attention to failures and complaining at folks :)13:15
ograasac, no, he couldnt13:15
ograthere was a bad bug that made many desktops freeze13:16
ograhe and bratsche worked on it for days now13:16
* ogra was affected 13:16
ograBug 52394913:16
ubottuLaunchpad bug 523949 in gtk+2.0 "the csd changes make some desktop applications hog the cpu" [High,Fix released] https://launchpad.net/bugs/52394913:16
ograso the upload was essential13:17
asacogra: right13:17
asacok13:17
ogralets see if ubuntu6 gets through13:17
ograi'll catherd it13:17
asacso we need to work on gtk and then wrap up the ftbfs list from there13:17
asacogra: you said indicators are really failing to build?13:17
ograNCommander, dyfet please take a look at gnome-keyring and the two indicators13:17
persiagtk and kdebindings should handle most of it.13:17
ograasac, indicator-sound at least13:17
ograi think there was another one13:17
* ogra looks13:17
asacchecking for SOUNDSERVICE... configure: error: Package requirements (dbusmenu-glib >= 0.1.1 indicator >= 0.3.0 libpulse-mainloop-glib >= 0.9.1913:18
asacfeels like something out of date13:18
dyfetNCommander: ok13:18
ograah, only -sound now13:18
persiaThat's probably related to the recent pulse update.13:18
persia(press the shiny button)13:19
ograi gave it back already once13:19
asacok I look into gtk and indicator build failures with dyfet and maybe NCommander13:19
asaclets move on13:19
asac*  Team to add individual summaries to standing items before meetings.13:19
ograi'll care for gtk13:19
asacreminder: please do that ;)13:19
* NCommander did :-)13:19
StevenKHint: it's no longer before the meeting13:19
ogranext time, sorry ... /me missed13:19
asaceveryone  missed.13:19
asacso whip cracking: that would be really cool to have ;)13:20
asacyou can also include that in the AR mail if you send one13:20
asacbefor the meeting13:20
asacNCommander: yes. you are great!!13:20
ogragood idea13:20
asac[TOPIC] Standing items13:20
MootBotNew Topic:  Standing items13:20
ograbah, lots of red13:20
asaclets take a last look at alpha-3 thing13:20
asac[LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html13:21
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-lucid-alpha-3.html13:21
asacso last week before release meeting i bumped a bunch o items to beta-113:21
asachttp://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html13:21
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html13:21
asaci made have made a mistake in syntax here and there13:21
asacplease ensure that all of the work items for alpha-3 are moved to ubuntu-10.04-beta-113:22
asac[ACTION] everyone to move work items not finished for alpha-3 to ubnutu-10.04-beta-113:22
MootBotACTION received:  everyone to move work items not finished for alpha-3 to ubnutu-10.04-beta-113:22
asacthe main two specs for beta-1 are webservice email/office.13:22
* ogra notes that apw just did that on the powermanagement one 13:22
* ogra hugs apw 13:22
asacthose will need to be finished by end of this week/early next week ... otherwise release team will kick me ;)13:23
ograwhat about the browser ?13:23
ograstill has many open items13:23
asaci have to check if they dropped the final comment13:23
asacsecurity team that is13:24
ograwas there a decision now ?13:24
asacas it stands now we consider chromium not supportable13:24
ograok13:24
asacwe will try to support it in universe and learn from it13:24
asacif all goes well, we can go for it next cycle13:24
persiaasac: You're keeping the MIR bug up to date about that?13:24
ogra++13:24
* persia knows that several external groups are subscribed13:24
asacpersia: that was the idea13:24
persiaCool!13:25
asacpersia: i asked kees to give a final statement from security team - which was supposed to happen on friday13:25
asaci have to check if that happened13:25
* persia checks the bug13:25
asacso yeah ... all the browser items will get done once that decision is there13:25
persia( bug #522645 for those who wish to follow along )13:25
asaceverything left there in my book was blocked by decision13:25
ubottuLaunchpad bug 522645 in chromium-browser "[MIR] chromium-browser" [Undecided,Incomplete] https://launchpad.net/bugs/52264513:25
asacok anything else on work itesm? anyone feels like they are out of work?13:26
ograonce rootstock is done i'll have some spare cycles13:26
ograi should be doen fully by end of the week with the GUI13:26
asacgood. with some luck those will be directly consumed by a new project ;)13:26
ograso feel free to put something up for me13:26
dholbachif anybody feels like they are out of work, I'd like to remind everybody of: http://people.canonical.com/~dholbach/sponsoring/ - it really needs some hands on deck no13:26
dholbach(and it lists unr packages too)13:27
* ogra tickles dholbach 13:27
* dholbach hugs ogra13:27
StevenKIt isn't UNR13:27
asacdholbach: can you ensure that sponsored uploads without bugs also get in the company sponsoring report ;)?13:27
asacthat reminds me ... dholbach was looking for open week contributions13:27
dholbachasac: sponsored uploads should get there13:27
asaccool13:27
dholbachhttps://wiki.ubuntu.com/Packaging/Training13:27
asacmaybe we can run a session on how to develop for arm using qemu static etc.?13:27
dholbachStevenK: sorry, I meant the 'unr' packageset13:27
=== fader|away is now known as fader_
asacdholbach: would that help?13:28
dholbachStevenK: which overlaps with other sets13:28
dholbachasac: that'd be cool13:28
dholbachasac: and I'll talk to bdrung too13:28
asac[ACTION] asac to talk to team about training session13:28
MootBotACTION received:  asac to talk to team about training session13:28
asacok moving on ;) ...13:29
dholbachthanks a lot everybody! and I hope there's many good fixes for *mobile* in the sponsoring queue13:29
asac[TOPIC] Standing Items - Kernel Status (cooloney, ericm)13:29
MootBotNew Topic:  Standing Items - Kernel Status (cooloney, ericm)13:29
cooloneyfor imx51 kernel,13:29
cooloneywe updated to latest fsl bsp release13:29
ograworks fine :)13:29
cooloneyafter fixing a compiling error (i sent that patch to fsl)13:30
ograthough i'D still like to see bug 457878 fixed before release13:30
ubottuLaunchpad bug 457878 in linux-fsl-imx51 "imx51 on board ethernet plug/unplug events not detected" [Medium,Confirmed] https://launchpad.net/bugs/45787813:30
cooloneyit was uploaded alreayd13:30
ogracooloney, a fix for that bug ?13:30
plarscooloney: did it make it in time for the A3 image?13:30
cooloneyand apw also applied 2 VFP sig patches13:30
ograthen it didnt work ... at least not in my tests13:31
ograi still dont see any plug/unplug events for the NIC13:31
cooloneyogra and plars, oh, it needs some work for a313:31
cooloneyi don't think we can make it13:31
asaccooloney: dodes that fix bug 507503 ?13:31
ograwell, i'm not concerned about A313:31
ubottuLaunchpad bug 507503 in linux-fsl-imx51 "VFP/NEON state is not preserved around signal handlers, causing state corruption between user processes" [High,In progress] https://launchpad.net/bugs/50750313:31
plarswe will retest in the following daily images then13:31
ograbut would like it for final13:31
cooloneythis bug is because fsl fec driver does not support link status change13:32
ograright13:32
cooloneyyeah, that VFP signal bug should be fixed in latest uploads13:32
asaccooloney: so VFP is in a3 ... bug 457878 is waiting for upstream fix?13:33
ubottuLaunchpad bug 457878 in linux-fsl-imx51 "imx51 on board ethernet plug/unplug events not detected" [Medium,Confirmed] https://launchpad.net/bugs/45787813:33
ogracooloney, did that also go into the SRU for karmic ?13:33
cooloneyogra: actually, i have not been thinking about karmic for a long time, heh13:33
ograwell, there was an SRU last week13:34
ografor the NEON stuff13:34
cooloneyogra: that is another bug13:34
persiaWell, except bug #507416 only contains half the fix for NEON, so it's not enough.13:34
cooloneybug 50741613:34
ubottuLaunchpad bug 507416 in linux-fsl-imx51 "CONFIG_NEON=y causes platform lockups with certain application/platform combinations" [High,Confirmed] https://launchpad.net/bugs/50741613:34
ograright, but wouldnt it affect karmic as well if NEON is used ?13:34
persiaSince we have to get something else into -proposed anyway, we may as well see if 457878 can be included then.13:35
cooloneypersia: i just talked with dmart13:35
persiacooloney: And?13:35
asaccooloney: according to bug 507503 ... the VFP thing isnt fixed in current archive version ... what was uploaded by apw ?13:35
ubottuLaunchpad bug 507503 in linux-fsl-imx51 "VFP/NEON state is not preserved around signal handlers, causing state corruption between user processes" [High,In progress] https://launchpad.net/bugs/50750313:35
cooloneyfor the 2nd patch, we found our workaround method does not work on imx51 A8 based soc13:35
ograasac, we just got as test request from him13:35
cooloneybecause we can not disable NEON hardware in kernel13:35
cooloneyby setting ASEDIS bit13:36
cooloneyASEDIS is only available in A9 processor13:36
dmartBut since karmic didn't have that anyway, we're not making it worse.13:36
* JamieBennett appears with new tires :)13:36
persiaOK.  So 507416 doesn't fix the issue, but there's no regression potential?13:36
dmartThere's no regression.13:37
dmartthis is a preexisting issue13:37
cooloneyright,13:37
cooloneyso i think currently we can't do anymore to workaround this issue on old silicon13:38
persiaOK.  Someone (who understands better than I) needs to update the bug with a comment explaining that it's unfixable with the current approach, but that the patch doesn't cause regressions, otherwise it will block the rest of the SRU kernel.13:38
asaccooloney: so you are saying tha the VFP part of 507503 is fixed , but NEON is not? maybe we should split this bug up so we can close the first half?13:38
asac(talking about lucid here)13:38
cooloneypersia: no problem, i will do that.13:39
cooloneyasac: yeah, patches are applied and kernel was uploaded13:39
dmartasac: 507503 is not neon-specific, it's just an issue common to NEON and VFP13:39
asaccooloney: why wasnt the bug closed in the upload then?13:39
cooloneyasac: that is because the 2 patches is from upstream13:40
asaccooloney: ok, so lets close the bug?13:40
cooloneywe applied them and don't want to change their description by adding our syntax such as BugLink13:40
asackk13:40
cooloneyso if there is no such BugLink, it will not be closed automatically13:41
cooloneyi will close it manually.13:41
asacthanks13:41
asacok ericm isnt here13:41
asacso we skip dove for now (maybe he will appear later)13:41
cooloneyno, he is on a business trip13:41
asacah right.13:42
asac[TOPIC] ARM Application status (JamieBennett, dyfet)13:42
MootBotNew Topic:  ARM Application status (JamieBennett, dyfet)13:42
cooloneybut if you guys have something, can tell me13:42
asaccooloney: thx13:42
cooloneyi will talk with him, since we are in the same TZ13:42
asacso think on the application front we are fine MINUS the webservices specs13:42
JamieBennett2D launcher fun13:42
asacnetbook-launcher even has 2d fallback13:42
asacah right ... go ahead JamieBennett13:42
JamieBennett2D launcher respawn problem is there13:43
asacright13:43
asacthats bug #52585413:43
ubottuLaunchpad bug 525854 in go-home-applet "with 2d launcher, go-home starts a new netbook-launcher-efl instead of bringing it to the front" [Undecided,Triaged] https://launchpad.net/bugs/52585413:43
JamieBennettweb office services have initial code available13:43
asacak ... will review it today13:43
JamieBennettneeds a little more work and integration13:43
JamieBennettotherwise looking semi-ok package wise13:44
JamieBennettgetting quite a few 2D launcher bugs though13:44
asacJamieBennett: oh, you already have packaging even?13:44
JamieBennettnot for web office meant image packages in general13:44
asacright13:45
asacok13:45
JamieBennettI'll package web office on Friday13:45
asacJamieBennett: so what are the most pressing bugs for launcher (besides the respawn issue)13:45
ograyeah 2D launcher will need a lot of work13:45
ograbugs are piling up13:45
asaci assume the scroll bar thing is one ... whats the bug id?13:45
ograhttps://bugs.launchpad.net/ubuntu/+source/netbook-launcher-efl13:45
ogra15 open bugs now13:45
JamieBennettI've seen log out bugs, the respawn, mounting issues (although there was a fix available for this)13:46
ograover the last week we got 10 new ones13:46
asacwe have 15 bugs there ;) ... piling up is different term ;)13:46
JamieBennettyeah13:46
asacok13:46
JamieBennettmaybe we need to review them one by one13:46
JamieBennettand decide what are blockers13:46
asac[ACTION] asac and JamieBennett to triage netbook-launcher-efl bugs13:46
MootBotACTION received:  asac and JamieBennett to triage netbook-launcher-efl bugs13:46
asacand forward accordingly13:47
JamieBennettindeed or help mterry out13:47
asac[LINK] https://bugs.launchpad.net/ubuntu/+source/netbook-launcher-efl13:47
MootBotLINK received:  https://bugs.launchpad.net/ubuntu/+source/netbook-launcher-efl13:47
asacok ... anything else on app?13:47
JamieBennettno, move on13:47
asaci think i missed the previous one ...13:48
asac[TOPIC] QA Status (GrueMaster, plars)13:48
MootBotNew Topic:  QA Status (GrueMaster, plars)13:48
plarsA3 alpha testing should start real soon13:48
plarsthere's a desktop image listed out there right now, please ignore13:48
ograasac, skipping FTBFS ?13:48
asacogra: i moved backwards13:48
plarsnetbook images should be available soon (?) anyone looking at the libgtk2.0 issue?13:48
ograah13:48
StevenKWhich will no longer work, since I just purged it off cdimage13:49
GrueMasterCouple of issues with the installer last week.  Hopefully they are fixed with the new images.  Fix was uploaded last night but I couldn't download all the packages to test due to availability.13:49
asacplars: do you have a link to the right qa tracker?13:49
ograplars, no issue just catherding the build, its on my list13:49
plarsasac: it should still be under the armel section on iso tracker13:49
plarshttp://iso.qa.ubuntu.com13:49
MootBotLINK received:  http://iso.qa.ubuntu.com13:49
plarsspecifically: http://iso.qa.ubuntu.com/qatracker/build/ubuntuarm/all13:49
NCommander(indiciator-sound is available for ARM now)13:50
asacGrueMaster: ok. maybe add a list of not yet fixed installer bugs to the QA status after the meeting13:50
asacGrueMaster: or after testing ;)13:50
asacNCommander: thanks!13:50
GrueMasterYes, after testing.13:50
asacwas there progress on all-pairs testing?13:51
ograNCommander, cool, leaves only keyring ...13:51
GrueMasterRead my status.13:51
NCommanderogra: looking at keyring now13:51
GrueMasterOr AR13:51
asacGrueMaster: we are here to report that ;)13:51
asacunless its added to the QA status13:51
GrueMasterOk.  No progress due to ubiquity issues.13:51
asacBug 52416913:52
ubottuLaunchpad bug 524169 in ubiquity "Ubiquity installer partitioner crashed, main installer enters endless loop" [High,Fix committed] https://launchpad.net/bugs/52416913:52
asacGrueMaster: that bug wsa discovered by all-pairs?13:52
asace.g. it doesnt show up in our normal image testing?13:53
GrueMasterThat bug was discovered before getting to the all-pairs selections.13:53
asacok13:53
GrueMasterI.e. That bug shows up in EVERY install test.13:53
asacanything else on QA?13:53
asacok lets move on ...13:54
asacthanks GrueMaster, plars13:54
GrueMasterX0 kernel fixed several bugs.  I retested several bugs filed prior to Sprint and marked them closed.13:54
asacgreat. thanks a lot13:54
asaci see that in your AR now13:54
asac[TOPIC] ARM Porting/FTBFS status (NCommander, dyfet)13:54
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)13:54
NCommanderindicator-sound fixed, looking at gnome-keyring13:54
asacNCommander: added it to the wiki13:55
asacand we already discussed a bit on gtk etc. above13:55
asacanything else?13:55
NCommanderw.r.t. to openoffice.org, I'm looking at bisecting binutils13:55
asacNCommander: did you create a wiki page for ooo?13:55
NCommanderasac: no13:55
asacwe should really document all the things we tried13:55
NCommanderasac: that's what the bug is for13:55
asac[ACTION] NCommander to create wiki page to track actions taken to evaluate ooo/uno issues13:55
MootBotACTION received:  NCommander to create wiki page to track actions taken to evaluate ooo/uno issues13:55
ograthe bug didnt have updates either :)13:56
asacNCommander: we want more than the bug imo ... unless you want to post all the steps done there even if they have no positive outcome13:56
* NCommander needs more external HDDs :-/13:56
NCommanderasac: that's the point of Launchpad; and having a bug. Take a look what I already posted13:56
asacok13:57
NCommanderAnyway, bisecting the toolchain has proven difficult on lucid due to thumb2 support lacking in binutils 2.1913:57
NCommanderSo I'm going to work against karmic on this13:57
ograone comment13:57
ograwhich was declined by doko13:57
NCommanderogra: you should also check the OOo bugtracker. I'll make sure to cross-post better13:58
ograright, on the bug itself there isnt much ...13:58
ograso the wikipage really makes sense13:58
asacNCommander: ok. so you are trying to bisect binutils now ... any other lead?13:58
asacNCommander: please keep everything in th elaunchpad bug13:59
asacNCommander: in the end we need to prove that we tried everything. i want all the bits together in one place13:59
NCommanderasac: well, I determined that we're dealing with some sorta stack corruption13:59
asacwhats the bug id? (would like to have it as link)13:59
ograBug 41700914:00
ubottuLaunchpad bug 417009 in openoffice.org "all openoffice apps die in 'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic" [High,Confirmed] https://launchpad.net/bugs/41700914:00
NCommanderYou can call into uno all you want, the abort comes when a process quits or something pops far enough in the stack to hit the corruption14:00
asac[TOPIC] openoffce uno issues14:00
MootBotNew Topic:  openoffce uno issues14:00
asachttps://launchpad.net/bugs/41700914:00
ubottuLaunchpad bug 417009 in openoffice.org "all openoffice apps die in 'com::sun::star::ucb::InteractiveAugmentedIOException' on armel in karmic" [High,Confirmed]14:00
asac[LINK] https://launchpad.net/bugs/41700914:00
MootBotLINK received:  https://launchpad.net/bugs/41700914:00
asacok ...anything else on ftbfs? (i think everything else needs to be discussed offline on ooo)14:01
asac[TOPIC] ARM Image Status (ogra, persia)14:01
MootBotNew Topic:  ARM Image Status (ogra, persia)14:01
ograimage from 22th looked ok ...14:01
ogratodays failed because of gtk14:01
persiaFor *all* the imags tha tbuilt.14:02
persiaBut why don't we have ubuntu-* or xubntu-* images for dove?14:02
asacwasnt xubuntu disabled?14:02
ograyeah14:02
persiaI had thought so, but it seems to have come back.14:02
asacalso i thought we wanted to stop producing ubuntu-14:02
GrueMasterImage from the 22nd had the installer bug.  Bug 52416914:02
ograwe'Re really short on livefs builder time14:02
ubottuLaunchpad bug 524169 in ubiquity "Ubiquity installer partitioner crashed, main installer enters endless loop" [High,Fix committed] https://launchpad.net/bugs/52416914:02
dmart20100222 has some issues (installer doesn't work and rsyslogd hogs the CPU) but I don't think those are armel-specific.14:02
ogradmart, the latter is14:03
asacrsyslogd?14:03
ograand the last kernel upload has a fix for rsyslogd14:03
persiaWell, it's kernel-specific to the armel kernel.14:03
ograyeah14:03
asacreally? i was told it was not arm specific ... rather old kernel14:03
persiaBut not otherwise arch-specific.14:03
ograasac, right, imx51 is .3114:03
dmartok; non-armel people were reporting it, but maybe on old kernels14:03
asacanyone has the bug number for rsyslogd?14:03
ograit needed a feature backported14:03
ograbug 52361014:04
ubottuLaunchpad bug 523610 in rsyslog "rsyslogd spins CPU on older kernels" [High,Triaged] https://launchpad.net/bugs/52361014:04
asac[LINK] https://launchpad.net/bugs/52361014:04
MootBotLINK received:  https://launchpad.net/bugs/52361014:04
ubottuLaunchpad bug 523610 in rsyslog "rsyslogd spins CPU on older kernels" [High,Triaged]14:04
ograapw is the hero that fixed it on the go :)14:04
persiadmart: Yes.  There's a few folk running .31 kernels (especially realtime users)14:04
ograpersia, which isnt supported anyway by words of Keybuk14:04
asacso anyone takes action to investigate why xubuntu etc. are built again?14:05
ograStevenK, ^^^ ?14:05
persiaogra: I've been told the opposite by rtg.  I suspect we need to bring them together.14:05
asac[ACTION] StevenK and persia to ensure that xubuntu- ubuntu- images are not produced for armel anymore14:05
MootBotACTION received:  StevenK and persia to ensure that xubuntu- ubuntu- images are not produced for armel anymore14:05
StevenKDon't bother, I just fixed it14:05
ograasac, -desktop was completely ripped out right before the meeting14:05
StevenKLike, ten minutes ago14:05
ograStevenK, xubuntu too ?14:05
persiaasac: Can we add kubuntu-desktop to that list, and only do *-netbook and server images?14:05
StevenKogra: I didn't bin the images, but I can14:06
ograyeah, they will be hevily outdated14:06
ograpersia, ++14:06
asac[ACTION] StevenK and persia to also get rid of kubuntu-desktop aka everything != server | netbook14:06
MootBotACTION received:  StevenK and persia to also get rid of kubuntu-desktop aka everything != server | netbook14:06
asacanything else on image?14:07
ogranot from me14:07
asac[TOPIC] AOB14:07
MootBotNew Topic:  AOB14:07
asacanyone?14:07
ograplease test the GUI after my next rootstock upload  :)14:07
asac[ACTION] everyone to try rootstock GUI once its in the archive14:08
MootBotACTION received:  everyone to try rootstock GUI once its in the archive14:08
ograit is in the archive :)14:08
asaclatest14:08
GrueMasterogra: I have it on my todo for after Aplha 3.14:08
ogratry the 0.2.0 release :)14:08
asacgood. anything else?14:08
ograright, that upload wont happen during freeze anyway14:08
asacogra: rootstock is in main?14:09
asacon CD?14:09
ogranope14:09
asacjust upload14:09
ograand i dont want it in main yet :)14:09
asacits not covered by freeze then14:09
ograasac, indeed, but i'm busy with A3 stuff anyway14:09
asacthought its ready?14:09
asacanyway. do it when you have time ;)14:10
asacanything else for AOB?14:10
asac314:10
asac214:10
asac114:10
asac#endmeeting14:10
MootBotMeeting finished at 08:10.14:10
asacthanks all14:10
asacLogs available at http://www.novarata.net/mootbot/14:11
kees\o14:57
cjwatsonhi14:58
cjwatsonsabdfl sent apologies via randa14:58
cjwatsonmdz sent notification of attention being partially elsewhere14:59
cjwatsonand Keybuk hasn't been seen around on IRC for a while14:59
pittio/14:59
pittihm, 3 is not quorum yet, is it?14:59
cjwatsonI think the TB has traditionally considered 50% as quorum15:00
cjwatsonwith any luck mdz will be available for votes15:00
mdzcjwatson, maybe15:01
mdzIMO 3 is a quorum though15:01
keeswe'd never have meetings if we didn't consider 50% as quorum.  :P15:01
cjwatsonKeybuk isn't around, and I don't think I can effectively chair - too much of my head is occupied trying to work out this crazy memory corruption in d-i15:02
keescjwatson: I can chair; I just can't find the Feb 9th meeting notes ... looking still15:03
cjwatsonthanks15:03
pittihm, I'm fairly sure I put them in, hang on15:03
keespitti: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-February/000673.html15:04
cjwatsonI am getting further and further down rabbit-holes here - current one is that newt doesn't seem to build for me15:04
keespitti: I didn't see them in https://wiki.ubuntu.com/TeamReports/February2010 though15:04
keesanyway,15:04
kees#startmeeting15:04
pittikees: https://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current15:04
MootBotMeeting started at 09:04. The chair is kees.15:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:04
cjwatsonthe agenda didn't seem to get flushed from last time15:04
cjwatsonmoment while I edit it?15:04
keespitti: "current" should be a link to the per-month report15:04
cjwatsonerr, highvoltage has it open15:04
highvoltagecjwatson: closing...15:05
highvoltagecjwatson: ok done15:05
cjwatsonthe first two items under archivereorg were done, anyway15:05
keespitti: i.e. echnicalBoard/TeamReports/10/February15:05
cjwatsonthanks15:05
kees+T15:05
keescjwatson: let me know when you're done with it15:06
cjwatsonok, done with the agenda now15:06
keesheh ok15:06
cjwatsonhttps://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current has been busted15:06
cjwatsonit used to be a redirect15:06
mdzcjwatson, kees, pitti, please mention me if you need my input on something, otherwise my attention will be on the phone15:06
pittimdz: unterstood, thanks15:06
cjwatsoncf. https://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current?action=diff&rev2=11&rev1=815:06
cjwatsonI will go and fix it up15:06
kees[TOPIC] Review actions from last meeting15:06
MootBotNew Topic:  Review actions from last meeting15:06
kees* kees to follow up with Debian TC on units policy15:07
keesI haven't heard anything new from bdale15:07
kees* cjwatson to follow up with mythbuntu-dev to get ubuntu-core-dev added15:07
cjwatsondone ages ago15:08
kees* ScottK to update Kubuntu/UpdatesPolicy based on Kubuntu upstream feedback15:08
keeslooks like this happened?15:08
keeshttp://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft15:08
MootBotLINK received:  http://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft15:08
Riddellkees: still needs approval upstream15:08
keesRiddell: ah, okay.15:09
kees* sabdfl to propose to CC that the TB is a CC delegate, and clarify his role15:09
cjwatsonI've fixed the team reports stuff15:09
keescjwatson: cool, thanks15:09
keesI don't know what happens at CC, so I don't know if the CC delegate thing has happened yet15:09
keeswere there other actions?  that's all I see from the last report15:10
pittiAFAIK these were the pending ones15:10
keesokay, cool15:11
kees[TOPIC] Have delegated teams become responsible for security of their packagesets15:11
MootBotNew Topic:  Have delegated teams become responsible for security of their packagesets15:11
keesso, this came up while trying to figure out how motu-swat (the MOTU security team) fits into archive-reorg15:11
cjwatsonare you including, say, ubuntu-core-dev? :-)15:11
keescjwatson: possibly, yes.15:11
cjwatsonwell, I was just wondering what was left for the security team to do then ;-)15:12
keesthey idea here is that teams should be responsible for security issues in their packagesets.15:12
keeswell, I was thinking that the Ubuntu security team still tracks CVEs globally, but would benefit from fixing help.15:12
cjwatsonit makes sense for teams to be paying attention to such things in a more organised fashion than right now; I'm not sure "responsible" is the right word, since I think the security team still has to be ultimate buck-stops-here15:13
keesyes, agreed; that language should change.15:13
mdzkees: I reordered the agenda to put the new topics ahead of the old; hope that's OK15:13
pittikees: I was going to say that I don't think it's very efficient to split tracking into multiple teams15:13
keesI think the idea was to try to spur more involvement.15:13
keesmdz: saw that, it's fine.15:13
pittibecause then the CVE triage would be done five times instead of once?15:14
cjwatsonand I like the idea of having somebody from each team actively engaged with the security team, provided that the security team assists them with tools15:14
* kees has chosen poorly wrt language here.15:14
pittikees: so you propose central tracking/distributed fixing? or distributed tracking as well?15:14
keesI would like to see delegated teams being _aware_ of CVEs in their packagesets.15:14
cjwatsonperhaps it would make sense for the security team to explicitly put things onto delegated teams' work lists, after triage?15:15
pittikees: aware == tracking, though?15:15
keespitti: yes, central tracking/distributed fixing.  especially true for non-seeded packages.15:15
pittiit's a huge difference between "dear desktop team can you please upload a fix for CVE-1234" or "please go find all that we need to fix"15:15
keespitti: I need to find language for "is aware of the CVE and thinking about how to fix it once the CVE has been identified by the security team, or the team becomes aware of a security issue and communicates it to the security team"15:16
pittiand my gut feeling is that centralized tracking is more efficient15:16
cjwatsonso, what specifically needs to change?  somebody in each team (default: team lead) should take responsibility for liaising with the security team, and is expected to have mail filters such that they see CVEs as a priority, something like that?15:16
pittikees: ok, understood you15:16
keesI do not want the teams CVE-hunting; there is a good centralized process for that.  at the same time, I don't want them to ignore new security issies if they just happen to not yet have a CVE.15:16
keescjwatson: I'm looking to define what needs to be changed so that there is more team involvement, yes.15:17
cjwatsonpresumably responsible people are doing much of this already, with the exception of actively turning up to security team meetings15:18
cjwatsonare there groups of people who are being less responsible whom you're trying to address with this?15:18
keescjwatson: perferrably, they would watch the exported package CVE lists and take action when CVEs appear.  e.g. http://people.canonical.com/~ubuntu-security/cve/pkg/linux.html15:18
keesno, it's to better define how security is handled once the main/universe distinction fades.  from there, it seems like the ubuntu-security-sponsors (or some other team like motu-swat) would become responsible for unseeded packages15:19
keesthat said, there isn't a lot of interest in backporting fixes beyond the latest stable by devel teams, which I understand.15:20
keesbut that's where the U.S.T. does more of its work too15:20
cjwatsonso you'd be most interested in teams basically looking down the right-hand column of the CVE lists?15:21
cjwatsoni.e. lucid15:21
keeswell, I'd prefer they look at the entire table.  right now, most devel teams are only interested in the right-hand column; I'd like to fix that.15:21
pittithat seems to tie in with the question how long (and in which releases) a particular package gets security updates in the first place; this varies for each delegated archive area15:21
keesright15:22
pittiin main/universe this is very clear15:22
pittiin the new world, we could say that the Canonical security team only covers core ("foundations")/desktop/kubuntu15:22
pitti../server15:22
pittitogether with appropriate EOL dates15:23
cjwatsonright, products we ship as a company.15:23
pittithis would keep the intention that what we call "universe" today still doesn't get under the umbrella of 18 month support15:23
cjwatsonso I think this is good as a general idea, but it could use work on the presentation, and probably refinement with individual teams15:24
cjwatsonkees: have you spoken to any of the delegated teams in question as yet, aside from motu-swat?15:24
keesanyway, I'm not sure the best language for making a recommendation, but wanted to bring up the idea.15:24
pittiI certainly would like to avoid getting into a situation where we (as in "all Ubuntu developers") have to support the entire archive for 18/36/60 months15:25
keescjwatson: I have not, no.  the idea formed yesterday with persia at the UST meeting15:25
keescjwatson: what do you recommend as the best forum for discussing this further?15:25
cjwatsonnot sure.  either speaking with teams one at a time, or ubuntu-devel, I suppose15:26
cjwatsonit might be a good idea to talk individually with some of the biggest teams (e.g. Kubuntu) first?15:26
cjwatsonand see what they make of it in practice15:26
keesdid the list of delegated teams end up in the wiki at some point?  /me has a memory of this15:26
pittikees: it's on https://wiki.ubuntu.com/DeveloperMembershipBoard15:27
pitti#Delegation15:27
pittiplus MOTU15:27
keesah-ha, thanks.  okay, I've burned plenty of time, I'll email teams and ubuntu-devel.15:27
kees[topic] Package set for CLI packages (Iain Lane)15:27
MootBotNew Topic:  Package set for CLI packages (Iain Lane)15:27
keesLaney: you're up15:28
cjwatsonjust a nitpick, perhaps we can call this CLI/Mono or something?  I keep looking at it and thinking "command-line interface"15:28
* kees too.15:28
LaneyHiya15:28
keesI'm generally in favor of a dedicated CLI/Mono team15:29
LaneyI don't know if the process is at the stage where we can have teams like this15:29
Laneybut I thought I'd put it out there15:29
LaneyCLI/Mono is alright with me if it makes things clear (we could conceivably get other runtimes in the future though)15:29
cjwatsonwe'll be inventing process a bit on the fly since this would be the first team of this category on this scale, but that's OK, we always meant to do it anyway15:30
Laneysure15:30
cjwatsonone or two of the individual packages listed seemed a bit odd; isn't antlr a Java thing? and launchpad-integration is pretty core, even if it does have a -cli bit15:30
LaneyYeah. It's just a list of rdeps which I pruned a bit (removing OOo and some others). We can take out various ones which provide just b indings15:30
keesgmime* is probably another one15:31
cjwatsonI think I'd like to remove the ones that have a single CLI binary package among lots of other bits; but I'm comfortable with the general idea15:31
Laneywe've previously had to touch gmime in the past, but yeah. gmime*, indicator-application, lp-i, antlr15:31
Laneythose are the ones I see immediately that might be questionable15:32
pitticjwatson: just to ensure, packages can be in arbitrarily many package sets, right?15:32
cjwatsonyes15:33
LaneyWill the set of uploaders be the union of the uploaders to the sets?15:33
cjwatsonI'm also comfortable with all of the individuals listed15:33
cjwatsonLaney: yes15:33
LaneyGood, that's what I thought15:33
pittilike, tomboy could be in both desktop and cli/mono15:33
cjwatson(modulo details about "restricted sets", of which there are currently none unless I miss my guess)15:33
LaneyI don't know if anyone is uncomfortable about mono, f-spot and the like though15:33
Laneyhopefully not...15:33
cjwatsonI don't know who else would maintain mono in practice if it weren't the set of people I see listed here15:34
pitticjwatson: reason I ask is that it becomes a bit confusing when we need to define the support status of that set (since there's both unsupported and desktop-supported bits in there15:34
Laneyyes, and that is how it has been done in practice, albeit with core-devs gatekeeping15:34
cjwatsonpitti: we're allowed to have package sets that are just for upload purposes, and don't have a homogeneous support status15:34
pittigreat15:34
LaneyI don't see it changing the support status indeed15:35
keessounds like next steps are: prune the package list more, then vote on the delegation? so perhaps iterate via email?15:35
cjwatsonok, subject to a revised package list from Laney, there seems no substantial disagreement15:35
cjwatsonshall we just vote pending that?15:35
Laneymembership procedure?15:35
LaneyIs there a policy for this already?15:35
cjwatsonyour comment about delegating to the DMB seemed reasonable15:35
LaneyI guess it would just extend the PPU policy15:36
cjwatsonthe DMB can handle it like other applications (motu, core-dev)15:36
Laneycool15:36
cjwatsonwith appropriate revision of expectations15:36
Laneyand what about adding packages in the future. Can this be done informally?15:36
cjwatsonquestion: who should handle extensions of the package set (as opposed to the uploader set)?15:36
Laneysnap15:36
cjwatsonsnap15:36
persiaTB15:37
cjwatsonthere is no particular precedent for this15:37
persiaErr, TB+~ubuntu-archive15:37
cjwatsonwell15:37
cjwatsonfor the kernel, and I think for printing, we named the category of packages quite explicitly, and so it's straightforward for an archive admin to add packages based on that understanding15:37
pitticonceptually it seems similar to adding people as PPUs15:37
cjwatsonfor instance it's entirely clear that linux-backport-modules-2.6.32 should have been added to the kernel package set to go alongside linux-backports-modules-2.6.31, and I did that without seeking confirmation15:38
keestwo votes now, then?  "creation of CLI/Mono team with [members], pending TB agreement on delegated package list" and "CLI/Mono team membership is delegated to DMB" ?15:38
cjwatsonI'm not sure that we can do that quite so clearly here, and thus having TB confirmation seems reasonable for now; we could do it by mail rather than in meetings though15:38
Laneythere is, for example, an upload of Docky which will happen soon (was rejected yesterday). This is clearly something for the set to have.15:39
cjwatsonany yea/nay on my made-up-on-the-spot process summary?15:39
cjwatsonwe could make it DMB confirmation rather than TB confirmation if people prefer15:39
cjwatsonalthough that constitutes the DMB extending its own delegation, so maybe not15:39
pittiI'd be fine with either of them15:39
keesme too15:39
pittisince DMB can already approve PPU15:40
Laneymaybe TB email confirmation?15:40
LaneyI don't have a real opinion15:40
cjwatsonlet's go with TB e-mail confirmation for now, and we can revisit as necessary?15:40
pittibut most additions should be quite obvious, so a simple confirmation ought to be enough15:40
cjwatsonkees: votes> sounds good15:40
pitticjwatson: sounds good15:40
keesokay, three votes, adding "packageset extension of CLI/Mono team done via TB e-mail confirmation"15:40
kees[vote] creation of CLI/Mono team with sebner directhex raof hyperair laney, pending TB agreement on delegated package list15:41
MootBotPlease vote on:  creation of CLI/Mono team with sebner directhex raof hyperair laney, pending TB agreement on delegated package list.15:41
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:41
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:41
pitti+115:41
MootBot+1 received from pitti. 1 for, 0 against. 0 have abstained. Count is now 115:41
keesmdz: this is to vote on the membership listed in https://lists.ubuntu.com/archives/technical-board/2010-February/000094.html15:41
kees+115:41
MootBot+1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 215:41
* hyperair wonders if i can vote15:41
cjwatson+115:42
MootBot+1 received from cjwatson. 3 for, 0 against. 0 have abstained. Count is now 315:42
keeshyperair: mootbot will count you, but it doesn't count in the TB vote-count.  :)15:42
hyperairheheh okay =p15:42
keeswe can check in with mdz later15:42
kees[endvote]15:43
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 315:43
kees[vote] CLI/Mono team membership is delegated to DMB15:43
MootBotPlease vote on:  CLI/Mono team membership is delegated to DMB.15:43
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:43
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:43
mdzkees: given I'm not paying attention, I abstain15:43
keesmdz: ok15:43
kees+115:43
MootBot+1 received from kees. 1 for, 0 against. 0 have abstained. Count is now 115:43
pitti+115:43
MootBot+1 received from pitti. 2 for, 0 against. 0 have abstained. Count is now 215:43
mdzthis one is a general governance question, so I'll vote15:43
mdzand I'm +115:43
mdz+115:43
MootBot+1 received from mdz. 3 for, 0 against. 0 have abstained. Count is now 315:43
cjwatson+115:44
MootBot+1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 415:44
kees[endvote]15:44
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 415:44
kees[vote] packageset extension of CLI/Mono team done via TB e-mail confirmation15:44
MootBotPlease vote on:  packageset extension of CLI/Mono team done via TB e-mail confirmation.15:44
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:44
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:44
kees+115:44
MootBot+1 received from kees. 1 for, 0 against. 0 have abstained. Count is now 115:44
cjwatson+115:44
MootBot+1 received from cjwatson. 2 for, 0 against. 0 have abstained. Count is now 215:44
pitti+115:44
MootBot+1 received from pitti. 3 for, 0 against. 0 have abstained. Count is now 315:44
kees[endvote]15:44
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 315:44
cjwatsonhooray for unanimity15:44
keeswheee, cli/mono team!15:44
pittiLaney: thanks for bringing this up15:44
directhexwell that was pretty painless. my thanks, ladies & gents15:45
Laneythat was smooth, thanks guys15:45
hyperair\o/15:45
pittiLaney: this seems to be an exemplary team wrt. Debian/Ubuntu cooperation :)15:45
directhexespecially to Laney for writing the proposal15:45
Laneypitti: we do try hard to achieve this15:45
* hyperair agrees with directhex15:45
cjwatsonpitti: agreed, I've been very impressed indeed15:45
keesok, so, we'll continue the package list via email.  I'm going to run the agenda ahead, as we're going to run out of time.15:46
kees[topic] Ubuntu IRC Council Access level in #ubuntu-devel (Jussi Schultink)15:46
MootBotNew Topic:  Ubuntu IRC Council Access level in #ubuntu-devel (Jussi Schultink)15:46
jussi01o/15:46
jussi01SO, after the email, any questions?15:46
mdzlooks like folks are reading it :-)15:47
keesthis seems clear to me.  I don't think we need a vote, just someone with perms to make it happen.15:47
mdz[link] https://lists.ubuntu.com/archives/technical-board/2010-February/000095.html15:47
MootBotLINK received:  https://lists.ubuntu.com/archives/technical-board/2010-February/000095.html15:47
cjwatsonI have no particular problem with this; IIRC last time there were some problems with the IRCC, but all that seems to have quietened down15:47
cjwatsonI can implement it if the TB is in agreement15:48
pittino objection here15:48
kees[vote] implement IRC Council Access on IRC15:48
MootBotPlease vote on:  implement IRC Council Access on IRC.15:48
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:48
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:48
kees+115:48
MootBot+1 received from kees. 1 for, 0 against. 0 have abstained. Count is now 115:48
cjwatson+115:48
MootBot+1 received from cjwatson. 2 for, 0 against. 0 have abstained. Count is now 215:48
pitti+015:48
MootBotAbstention received from pitti. 2 for, 0 against. 1 have abstained. Count is now 215:48
pitti(admittedly I don't understand how the IRC administration works, abstaining)15:49
jussi01Do we need something from mdz then?15:49
* kees hopes mdz agrees15:49
mdz+015:49
MootBotAbstention received from mdz. 2 for, 0 against. 2 have abstained. Count is now 215:49
pittibut to me it didn't seem to be something that TB needs to vote on in the first place15:49
kees[endvote]15:49
MootBotFinal result is 2 for, 0 against. 2 abstained. Total: 215:49
cjwatsonout of curiosity, how does the "UbuntuIrcCouncil" mask work?15:49
cjwatsoni.e. how does one see what Freenode considers that to mean?15:50
cjwatsonis it just a shared account or something?15:50
jussi01cjwatson: its a registered nick that is identifyable to, and ubottu can identify to it to change things if a change is made on the LP team15:50
keesiiuc, it's a nick, so anyone with access to it?15:50
cjwatsonok15:51
cjwatsonI've implemented the requested change now15:51
jussi01thank you15:51
PiciOnly the IRCC has the password.15:51
keesthanks!15:51
kees[topic] Review UEC/Images/RefreshPolicy15:51
MootBotNew Topic:  Review UEC/Images/RefreshPolicy15:51
cjwatsonI assume you change it when the IRCC membership changes15:51
Picicjwatson: Yes.15:52
jussi01cjwatson: of course15:52
jussi01:)15:52
smoserI hope that everyone has had a chance to read https://wiki.ubuntu.com/UEC/Images/RefreshPolicy15:52
kees[link] https://wiki.ubuntu.com/UEC/Images/RefreshPolicy15:52
MootBotLINK received:  https://wiki.ubuntu.com/UEC/Images/RefreshPolicy15:52
smoserit has been here once before, and I believe that all points brought up were addressed.15:52
smoser(I had sent an email on Feb 11 to technical-board with info also)15:53
cjwatsonI have one query, which probably just reflects my ignorance: are people likely to have built their own AMIs based on those we ship (is that possible)?  in other words, would those people essentially be expected to refresh their AMIs once a month?15:53
smoserit is possible and likely15:53
mdzcjwatson, it is possible, but we are finding it more common/preferable that they are deriving "on the fly"15:54
smosercjwatson, for those people, the only time when they'd need to use a new image is when the updates were not possible via 'apt-get upgrade'15:54
mdzi.e. the instance boots our vanilla image, and is customized at boot time using puppet, chef, or similar15:54
mdzthat way, it is easy to swap out the underlying base image for updates15:54
mdzthat seems to be the more popular approach in the community today15:55
cjwatsonok, thanks for the clarification15:55
mdzpeople will create their own AMIs as well, but I think they're more or less on their own at that point15:55
smoserand, as mdz points out, if they're rebundling hopefully their rebundling process takes a AMI as input and works from that, so they could just drop in the new reference image.15:55
cjwatsonyou seem to have covered all the bases I can think of15:56
cjwatsonhow often do daily builds for lucid fail?15:56
mdzit looks good to me15:56
cjwatsonIOW how much handholding does it tend to need?15:56
smosercjwatson, they're fairly good. i'd say over 90% is a conserviative success rate guess15:57
keesthis all reads well to me.  I like the query tree on uec-images.u.c.  a few questions: 1) will cloud-utils be backported to hardy?  (does it need to be?)  2) should there be a mailing list to send details of the updates to? (like the USN mailing list for security updates?)15:57
cjwatsonthat's actually very good compared to e.g. CD image builds15:57
cjwatsonI guess you have a smaller software base going into them15:57
smoserkees, i have no plans to backport the cloud-utils to hardy or karmic, but it is very light and could be easily done.15:57
smoserthe "updates notification" was a new feature for lucid.15:57
* kees nods15:58
smosercjwatson, yeah, the "desktop" build fails more often.15:58
smoserkees, for number 2, once we get all this solidified and the QA team takes over, the intent is to announce on the Release blog, if that suitable15:58
smoserand very easily we can send that same message to appropriate mailing lists.15:59
keessounds fine15:59
keesshould we vote on this, or was the intention to just have TB review it?15:59
smosermdz, ?^16:00
mdzkees: we should vote on it16:00
mdzsmoser brought it here for approval16:00
keesok, the agenda just said "review", I wasn't sure.16:00
kees[vote] approve the UEC/Images/RefreshPolicy16:01
MootBotPlease vote on:  approve the UEC/Images/RefreshPolicy.16:01
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot16:01
MootBotE.g. /msg MootBot +1 #ubuntu-meeting16:01
kees+116:01
MootBot+1 received from kees. 1 for, 0 against. 0 have abstained. Count is now 116:01
mdz+116:01
MootBot+1 received from mdz. 2 for, 0 against. 0 have abstained. Count is now 216:01
pitti+116:01
MootBot+1 received from pitti. 3 for, 0 against. 0 have abstained. Count is now 316:01
mdzcjwatson, ?16:01
cjwatson+116:01
MootBot+1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 416:01
kees[endvote]16:02
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 416:02
keesokay, we're out of time today.  chair for next meeting, is, I assume, Keybuk again?16:02
highvoltageany chance we could get feedback from the edubuntu-dev application by e-mail?16:02
dholbachand the sponsoring bits :)16:03
cjwatsonhighvoltage: I'll try to do that16:03
cjwatson(at least)16:03
highvoltagecjwatson: thank you16:04
keesokay, thanks everyone. sorry for not getting through everything; we can continue some of it in email.16:04
kees#endmeeting16:04
MootBotMeeting finished at 10:04.16:04
pittithanks everyone16:05
pace_t_zuluman...16:11
pace_t_zului missed that meeting16:11
=== Tonio__ is now known as Tonio_
=== jono_ is now known as jono
=== jono is now known as Guest66435
bjfRoll Call17:02
* ogasawara waves17:02
* smb waves17:02
* tgardner pops in17:03
* amitk stumbles in17:03
* cking waves too17:03
bjf#startmeeting17:03
MootBotMeeting started at 11:03. The chair is bjf.17:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:03
* jjohansen waves17:03
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:03
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting17:03
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid17:03
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid17:03
bjfNOTE: '..' indicates that you are finished with your input.17:03
bjfNOTE: JFo is not joining us today. However, I have his data for the topics he is responsible for.17:04
bjf[TOPIC] Open Action Item: None17:04
MootBotNew Topic:  Open Action Item: None17:04
bjf[TOPIC] Release Metrics:17:04
MootBotNew Topic:  Release Metrics:17:04
bjfBugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)17:04
bjfRelease Meeting Bugs (4 bugs, 5 blueprints)17:04
bjf===17:04
bjfAlpha 3 Milestoned Bugs (24 bugs against all packages (down 1))17:04
bjf * 2 linux kernel bugs (up 1)17:04
bjf * 3 linux-fsl-imx51 bugs (no change)17:04
bjf * 0 linux-ec2 bug (no change)17:04
bjf * 1 linux-mvl-dove bugs (down 1)17:04
bjf===17:04
bjfRelease Targeted Bugs (137 bugs against all packages (up 5))17:04
bjf * 15 linux kernel bugs (up 1)17:04
bjf * 3 linux-fsl-imx51 bugs (down 1)17:04
bjf * 0 linux-ec2 bug (no change)17:04
bjf * 1 linux-mvl-dove bugs (down 1)17:04
bjf===17:04
bjfMilestoned Features -17:05
bjf * 0 blueprints17:05
bjf===17:05
bjfBugs with Patches Attached:112 (not counting Fix Committed)(up 5)17:05
bjfhttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on17:05
bjfBreakdown by status:17:05
bjfhttp://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/17:05
MootBotLINK received:  http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/17:05
bjf== Blueprints ==17:05
bjfkernel-lucid-bug-handling:17:05
bjf * No update, all items are still in progress.17:05
bjf[TOPIC] Blueprints: kernel-lucid-bug-handling (JFo)17:05
MootBotNew Topic:  Blueprints: kernel-lucid-bug-handling (JFo)17:05
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling17:05
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling17:05
bjf * No update, all items are still in progress.17:05
bjf[TOPIC] Blueprints: kernel-lucid-review-of-ubuntu-delta (apw)17:05
MootBotNew Topic:  Blueprints: kernel-lucid-review-of-ubuntu-delta (apw)17:05
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta17:05
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta17:05
apwdrbd confirmed no longer in user with the server team and dropped from the kernel.  Awaiting testing on the Lenovo driver combination which should close the last item here.17:05
apw..17:05
bjf[TOPIC] Blueprints: kernel-lucid-kernel-config-review (apw)17:06
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review17:06
MootBotNew Topic:  Blueprints: kernel-lucid-kernel-config-review (apw)17:06
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review17:06
apwIt seems we require SECCOMP enabled for Lucid, this is there for the distro kernels but under investigation for ARM.17:06
apw..17:06
bjf[TOPIC] Blueprints: kernel-lucid-kms (sconklin / apw)17:06
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms17:06
MootBotNew Topic:  Blueprints: kernel-lucid-kms (sconklin / apw)17:06
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms17:06
apwUpstream for DRM and upstream for the main drivers of interest, i915 and ATI, are all disavowing 2.6.32 indicating there is no hope of getting this working.  As we are already backporting Nouveau from 2.6.33 we are now examining the feasability of a wholesale DRM backport as a better starting point.  Testing ongoing, though all new issues are being shown up by this combination.17:07
apw..17:07
sconklinsconklin ..17:07
bjf[TOPIC] Blueprints: kernel-lucid-suspend-resume (manjo)17:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:07
MootBotNew Topic:  Blueprints: kernel-lucid-suspend-resume (manjo)17:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:07
bjfskipping for now17:08
bjf[TOPIC] Blueprints: kernel-lucid-apparmor-development (jjohansen)17:08
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development17:08
MootBotNew Topic:  Blueprints: kernel-lucid-apparmor-development (jjohansen)17:08
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development17:08
jjohansenFinally got another push to LKML out, working through the feedback.17:08
apwyour update is now in the archive in lucid17:08
jjohansenthanks17:09
amitkso we basically run AA-crack-of-the-day in lucid?17:09
jjohansenI should have another pull request this week17:09
apwAA upstream version is what we have17:09
* amitk realises that sounded negative, it wasn't meant to be17:09
jjohansenamitk: well mostly crack of the day, is cleanups and code transforms requested by upstream17:09
apwso we are testing whatever jj is pushing17:10
amitkcool17:10
amitk..17:10
jjohansen..17:10
bjf[TOPIC] Blueprints: kernel-lucid-suspend-resume (manjo)17:10
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:10
MootBotNew Topic:  Blueprints: kernel-lucid-suspend-resume (manjo)17:10
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:10
manjonothing more from last week17:10
manjo..17:10
bjf[TOPIC] Blueprints: kernel-lucid-boot-performance (apw, csurbhi)17:10
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance17:10
MootBotNew Topic:  Blueprints: kernel-lucid-boot-performance (apw, csurbhi)17:10
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance17:10
apwWe remain around the 1.6s to rootfs mark.  khubd fixes are now uploaded and looking good.17:11
apw..17:11
bjf[TOPIC] Other Release Tasks: Lucid Audio Support (bjf)17:11
MootBotNew Topic:  Other Release Tasks: Lucid Audio Support (bjf)17:11
bjfnothing new from last week17:11
bjf..17:11
bjf[TOPIC] Other Release Tasks: Lucid Better Power Mgt (amitk)17:11
MootBotNew Topic:  Other Release Tasks: Lucid Better Power Mgt (amitk)17:11
amitkno progress17:11
amitk..17:11
bjf[TOPIC] Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)17:12
MootBotNew Topic:  Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)17:12
jjohansenwell I poked at running a pv-ops kernel again briefly, it looks promising but I need to make sure I run through all zones, and regions17:12
jjohansenwhat do we want to do if the pv-ops kernel is working?17:13
bjf[TOPIC] Status: Lucid (apw)17:13
MootBotNew Topic:  Status: Lucid (apw)17:13
apwLucid is at stable v2.6.32.8, the khubd fixes have now hit the archive and boot times are looking better.  We have potential issues with the HDA beep being discordant and loud, but this seems to be codec specific and not the nightmare screech issue we have had before, investigation ongoing.  We also have graphics issues as discussed above, a decision will have to be taken in the next week as to direction.17:13
bjfsorry, still with jjohansen17:13
apw.... screech17:14
apwjjohansen, i presume that is much closer to the normal kernel?17:14
jjohansenit would be nice to dump the xen patchset but it is getting aweful late17:14
apwso we could get rid of the -ec2 kerenls?17:14
jjohansenpossibly17:14
jjohansenI still need to do a lot more testing to be sure17:14
apwwe might need to FF the change, but if it means we don't need more than a flavour then its worth it17:14
jjohansenI redid pv-ops with some of the configs that we learned are problematic disabled17:15
jjohansenwell we would need a flavour but not a topic branch17:15
apwright a flavour is much less maintenance overhead ... a _lot_17:15
jjohansenright17:15
apwso when can we get a definative answer as to whether its psosible17:16
apwi recon we'd need to make the decision at least a week before b-117:16
jjohansenwell I can make it high priority and know in a couple days17:16
jjohansenwill also want to discuss with the server team17:16
apwnext week sounds fine to me ... yeah lets get the people who care in a room and make them test it17:16
jjohansenokay, will do there is a server team meeting tomorrow17:17
jjohansen..17:17
bjfapw, back to you and Lucid status17:17
* apw repeats for sanity17:17
apwLucid is at stable v2.6.32.8, the khubd fixes have now hit the archive and boot times are looking better.  We have potential issues with the HDA beep being discordant and loud, but this seems to be codec specific and not the nightmare screech issue we have had before, investigation ongoing.  We also have graphics issues as discussed above, a decision will have to be taken in the next week as to direction.17:18
apwProgress has been pretty solid the last week, with us nearly hitting the trend-line for a day.  The new issues above have pushed us back a little.  I have been through the remaining Alpha-3 items and pushed any that are clearly not release critical out to ubuntu-10.04-beta-1, these include the apport changes etc which can easily be done after kerenel freeze.  If I have pushed your items out and they are kernel related we do need something soon; be17:18
apwta-1 is only 3 weeks out.17:18
apw..17:18
bjf[TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb)17:18
MootBotNew Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb)17:18
smbDapper:      2.6.15-55.82  (security)17:19
smbHardy:       2.6.24-27.65  (security)17:19
smb             2.6.24-27.67  (proposed)[0]   0/ 3 verifications done (+0)17:19
smbIntrepid:    2.6.27-17.45  (security)17:19
smbJaunty:      2.6.28-18.59  (security)17:19
smbKarmic:      2.6.31-19.56  (security)17:19
smb             2.6.31-20.57  (proposed)[15]  5/19 verifications done (+0)17:19
smb - LBM       2.6.31-20.22  (proposed)[15]  0/ 2 verifications done (+0)17:19
smb - mvl-dove  2.6.31-211.22 (security)17:19
smb             2.6.31-211.23 (waiting for acceptance)17:19
smb - fsl-imx51 2.6.31-108.21 (security)17:19
smb             2.6.31-108.22 (proposed)[6]   0/ 1 verifications done (+0)17:19
smb - ec2       2.6.31-304.10 (security)17:19
smb             2.6.31-304.11 (proposed)[6]   0/ 1 verifications done (+0)17:19
smbThe mvl-dove upload is not processed, yet as there were questions about its17:19
smbimpact by pitti which have not been answered.17:19
smbWorking on getting a few more changes in Karmic proposed being verified.17:19
smbLikewise fsl-imx51 and ec2 interested parties should report back on the17:19
smbbugs in question.17:19
smb..17:19
apwwhats the outstanfing Q?17:19
apwon mvl-dove?17:19
smbapw, Why it is needed. What the impact is17:20
apwthat contained the VFP stuff yes?17:20
smbSomething about needing more memory17:21
smbI asked Eric in email to comment on it17:21
apwok ... thanks ... will look at the thread     ..17:21
smb..17:21
bjf[TOPIC] Incoming Bugs: Regressions (JFo)17:21
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)17:21
bjfIncoming Bugs17:21
bjf160 Lucid Bugs (up 30)17:21
bjfCurrent regression stats (broken down by release):17:21
bjf==== regression-potential (up 13) ====17:21
bjf  * 51 lucid bugs17:21
bjf==== regression-update (no change) ====17:21
bjf  * 9 karmic bugs17:21
bjf  * 5 jaunty bugs17:22
bjf  * 2 intrepid bugs17:22
bjf  * 1 hardy bug17:22
bjf==== regression-release (up 1) ====17:22
bjf  * 55 karmic bugs17:22
bjf  * 23 jaunty bugs17:22
bjf  * 11 intrepid bugs17:22
bjf  * 4 hardy bugs17:22
bjf==== regression-proposed (no change) ====17:22
bjf  * 1 karmic bug17:22
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)17:22
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)17:22
bjfLast week's BugDay was a success. Stats are available at:17:22
bjfhttp://qa.ubuntu.com/reports/jfo/kernel-bugday/20100216.html17:22
MootBotLINK received:  http://qa.ubuntu.com/reports/jfo/kernel-bugday/20100216.html17:22
bjfThe next Kernel BugDay is scheduled for next Tuesday the 2nd of March. The focus will be Bugs with patches attached.17:22
bjf[TOPIC] Open Discussion or Questions: Anyone have anything?17:22
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?17:22
* apw notes beta-1 is nearly here ...17:23
bjfonce...17:23
apwthose of you with investigate tasks will find they are moot pretty soon17:23
apw..17:23
bjftwice...17:23
bjfthanks everyone17:24
bjf#endmeeting17:24
MootBotMeeting finished at 11:24.17:24
ckingthanks bjf17:24
csurbhithanks bjf17:24
amitkthanks bjf17:24
=== dmart is now known as Guest81189
=== Guest81189 is now known as dmart_
=== noy_ is now known as noy
=== tsimpson is now known as Guest5579
=== fader_ is now known as fader|away
=== noy_ is now known as noy

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