=== mrevell is now known as mrevell-lunch
=== salgado-afk is now known as salgado
=== gmb_ is now known as gmb
=== mrevell-lunch is now known as mrevell
Fujisanits my party and i parallel park if i want to with Hobbsee D:16:50
* Hobbsee goes to hunt for some staff16:51
kiko-afkHobbsee, the queue page working for you?16:51
Hobbseekiko-afk: sec, going and hunting for stafff.16:51
Fujisani will tell you everyday for the rest of my life what Hobbsee did to me16:52
Fujisani will make sure you will be reported Hobbsee16:52
Fujisanlet them review this16:52
Fujisanwhat you did to me16:52
Hobbseei knew i liked having ops here.16:52
kiko-afkwhat's parallel parking?16:53
Hobbseehe's whinging because he got banned for trolling16:54
kiko-afkI wish I could ban trolls on launchpad16:54
Hobbseei wish i could get freenode to do what htey say they will, too.16:55
Hobbseeman, i hate being a woman in tech sometimes.17:01
kiko-afkHobbsee, there's a long series of articles on CACM about this recently17:03
Hobbseekiko-afk: oh?17:03
kiko-afkyeah, are you a subscriber?17:03
Hobbseenope - no idea what it is17:04
kiko-afkthe communications of the acm?17:05
=== kiko-afk is now known as kiko
Hobbseekiko: i haven't, no.17:21
Hobbseekiko: and i can't test the queue stuff now, we've released.17:22
Hobbseepresumably i'll be able to test toolchain-ey bits, if someone leaves it for me17:22
kikoHobbsee, well, you will be able to soon, anyway. :)17:22
Hobbseekiko: neat :)17:22
Hobbseekiko: why?17:22
kikobecause II will open, I'm hoping? :)17:22
Hobbseeoh right17:24
Hobbseesure, and hopefully i won't have gone mad by then.17:24
Hobbseekiko: anywya, where would i find the cacm?17:27
Hobbseeoh, my bad.17:27
kikoHobbsee, check out acm.org17:28
Hobbseekiko: yeah, found that much, sorry17:28
kikoHobbsee, didn't you do compsci?17:28
Hobbseekiko: i'm doing computing, yes.  not compsci as such.17:29
=== salgado is now known as salgado-lunch
=== Hobbsee is now known as foo___
=== foo___ is now known as Hobbsee
=== salgado-lunch is now known as salgado
* Rinchen checks for mootbot18:57
* Rinchen gets a drink18:58
kikoAND ACTION!18:59
MootBotMeeting started at 20:00. The chair is Rinchen.19:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:00
RinchenWelcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.19:00
Rinchen[TOPIC] Roll Call19:00
MootBotNew Topic:  Roll Call19:00
statikm e19:00
Rinchenreleases team is here... others?19:01
rockstar_I believe thumper has a holiday today19:01
Rinchenmthaddon ?19:01
Rinchenah right19:01
Rinchenso it is19:01
rockstar_So I think the remainder of bzrlp (all two of us) are here19:01
Rinchenoh sorry19:02
* barry already me'd19:02
Rinchenok then19:02
Rinchen[TOPIC] Agenda19:02
MootBotNew Topic:  Agenda19:02
Rinchen * Next meeting19:02
Rinchen * Actions from last meeting19:02
Rinchen * Oops report (Matsubara)19:02
Rinchen * Critical Bugs (Rinchen)19:02
Rinchen * Bug tags19:02
Rinchen * Operations report (mthaddon/herb)19:02
Rinchen * DBA report (stub)19:02
Rinchen * Sysadmin requests (Rinchen)19:02
Rinchen * New packages required (salgado)19:02
Rinchen * A top user-affecting issue (mrevell)19:02
Rinchen * Doc Team report (mrevell)19:02
Rinchen * Community procedure for unplanned downtime (mpt)19:02
Rinchen* some interesting topic (kiko)19:02
* kiko chuckles19:03
Rinchen[TOPIC]  * Next meeting19:03
MootBotNew Topic:   * Next meeting19:03
Rinchensame time, same place, next week19:03
kikoyeah, let's have a next meeting.19:03
Rinchenany obstacles present with that? :-)19:03
matsubaranext thursday is a brazilian national holiday, btw19:03
kikothose are the best meeting days!!19:04
BjornTthere's a public holiday next thursday for me19:04
matsubarabut I think I'll be around. thinking about swapping it19:04
Rinchenok then..19:04
cpro1I won't be here too.19:04
al-maisansame here ..19:04
al-maisanit's May 1st .. a public holiday in germany19:05
Rinchen[AGREED] meeting next week, same time, station - apologies: brazil, BjornT, al-maisan19:05
MootBotAGREED received:  meeting next week, same time, station - apologies: brazil, BjornT, al-maisan19:05
carlosI will not be here either. This is my last meeting as a Launchpad member19:05
statikcarlos: we will miss you!19:05
adeuringit's a holiyday for me too (thanks al-mainsan :)19:05
cpro1Rinchen: I'm not in br ;)19:05
flacosteactually, i think May 1st is a national holiday everywhere except for Canada, US (UK?)19:06
barrycarlos: !19:06
jtvstatik: "next time, don't miss"19:06
* mpt hugs carlos 19:06
* carlos will miss working with you too...19:06
* Rinchen sniffles.19:06
kikocpro1, it doesn't matter -- you follow brazilian holidays unless you explicitly request to change19:06
gmbMay 1st is not a UK holiday.19:06
Rinchencarlos, you'll have to joins us for the meeting19:06
mrevellflacoste: Not for UK We have it 5th May19:06
=== cpro1 is now known as cprov
* barry will take a holiday if flacoste will19:06
Rinchen[AGREED] germany off too19:06
MootBotAGREED received:  germany off too19:06
intellectronicagmb: i think the uk moves it to the next monday19:06
Rinchen[TOPIC]  Actions from last meeting19:06
MootBotNew Topic:   Actions from last meeting19:06
gmbintellectronica: Yep.19:06
Rinchenall of my actions from last week were completed.19:06
Rinchen[TOPIC] Oops report (Matsubara)19:06
MootBotNew Topic:  Oops report (Matsubara)19:06
carlosRinchen: I will try to ;-) but will miss the funny 'me' part :-)19:06
Rinchencarlos, you can still "me" :-)19:07
matsubaraToday's oops report is about bugs 220251, 221072, 22104719:07
cprovkiko: I've changed my address, it should be enough to follow local holidays, isn't it obvious ?19:07
carlosRinchen: thanks :-P19:07
ubotuLaunchpad bug 220251 in malone "Calculating subscribers for bugs with multiple tasks is expensive" [High,Fix committed] https://launchpad.net/bugs/22025119:07
ubotuBug 221072 on http://launchpad.net/bugs/221072 is private19:07
matsubarasalgado, should #220251 importance be higher? is it not causing inconvenience for marilize?19:07
kikocprov, nope19:07
matsubaraThe project group milestone is broken on edge. abel already fixed and the branch is on the pqm queue. (#221047)19:07
salgadomatsubara, the actual bug fix won't help marilize19:07
mptRinchen, next you'll be saying he can still fix bugs ;-)19:07
matsubaraThanks BjornT and kiko for fixing the timeouts on the bug page (#220251)19:07
salgadomatsubara, what we need to do is run a couple DELETES in production19:07
kikocprov, you need to explicitly say you want to change to observe other holidays19:08
intellectronicamatsubara: a fix for 220251 has landed (and another fix to that too)19:08
Rinchenmpt, I'm glad you caught  that ;-)19:08
SteveAcprov: watch out for queens day next week.  depending how centrally you live, it may be impossible to work.19:08
SteveAcprov: it's basically like carnival.19:08
cprovkiko: it's not time to discuss it.19:08
matsubaraintellectronica: right, this is more like a thank you notice :-)19:08
cprovSteveA: yes, I was warned :)19:08
matsubarasalgado: is that the db query in the LPProductionStatus page?19:09
cprovSteveA: to not go to Amsterdam, basically.19:09
salgadomatsubara, it is19:09
matsubarasalgado: ok, thanks then.19:09
matsubaraRinchen: I'm done here.19:09
Rinchenthanks matsubara19:09
matsubarathanks everyone19:09
Rinchen[TOPIC] Critical Bugs (Rinchen)19:09
MootBotNew Topic:  Critical Bugs (Rinchen)19:09
Rinchensame two19:10
Rinchen[LINK] https://bugs.edge.launchpad.net/launchpad/+bug/20665419:10
RinchenThis is the memory issue. flacoste, SteveA.  Any updated status?19:10
MootBotLINK received:  https://bugs.edge.launchpad.net/launchpad/+bug/20665419:10
flacosteRinchen: yes19:10
Rinchenthe other is for thumper and mhw who are not here19:10
Rinchen[LINK] https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/11862519:10
MootBotLINK received:  https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/11862519:10
flacostethe issue is with +bugs-text19:10
ubotuLaunchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [Critical,Confirmed]19:10
Rinchenso I'll skp that19:10
flacosteand I'm working on a work-around19:10
flacosteultimately, this view should be rewritten to not use SQLObject19:10
flacostebut raw SQL19:11
SteveAlet's not mention particular URLs here :-)19:11
flacosteor this funcitonality moved to API where everything will be batched19:11
flacostethat's it19:11
SteveARinchen: the result, operationally, is that from tomorrow or so, we should be back to having reliably stable app servers19:12
Rinchenflacoste, great thanks. Looking forward to seeing the results.19:12
Rinchenfantastic, thanks.19:12
Rinchen[TOPIC] Bug tags19:12
MootBotNew Topic:  Bug tags19:12
Rinchenthere are no proposed bug tags19:12
Rinchen[TOPIC] Operations report (mthaddon/herb)19:12
MootBotNew Topic:  Operations report (mthaddon/herb)19:12
herbCherry picks since last meeting: 2008-04-18: r6113 & r6110, 2008-04-21: loggerhead r156, launchpad-loggerhead r29 and r614119:12
herbCurrently two cherry picks pending. Barring any objections we'll hold off until tomorrow at the earliest for them due to hardy.19:12
herbBug #206654 continues to be an issue, though it appears that flacoste has had a breakthrough.19:12
herbThat's it from me and Tom unless there are any questions.19:12
ubotuBug 206654 on http://launchpad.net/bugs/206654 is private19:12
Rinchenthanks herb19:13
Rinchen[TOPIC] DBA report (stub)19:13
MootBotNew Topic:  DBA report (stub)19:13
stubI think all the DB reviews are done finally for this cycle. If you are not sure of the status of your patch, email me. I need to talk with bigjools re: archive permissions because I can't understand his email...19:13
stubThe DB server seems to be coping quite happily with the current load. This is good. This should also be the highest load we see for quite some time as we work on ways of distributing the load (unless someone manages to remove bottlenecks in the other systems ;) )19:13
salgadoherb, there are actually 3 cherry picks pending, no?19:13
bigjoolsstub: talk to me after this meeting19:14
herbsalgado, well the 3rd hasn't been approved19:14
herbsalgado, sorry, I should have clarified.19:14
salgadoherb, right, good point.  can you approve it kiko?19:14
Rinchenthanks stub19:14
Rinchenany questions for stub before I move on?19:14
kikosalgado, yeah, mats just asked me19:15
kikosalgado, I thought I had approved it. maybe my wiki edit conflicted and I didn't see that happen. it's approved.19:15
salgadokiko, he asked for approval for the pending SQL.  there's a cherry pick there as well19:15
Rinchen[TOPIC] Sysadmin requests (Rinchen)19:15
MootBotNew Topic:  Sysadmin requests (Rinchen)19:15
RinchenHi! Is anyone blocked on an RT or have any that are becoming urgent? I'm aware of the usual ones.19:15
kikosalgado, that I hadn't seen19:16
* Rinchen waves at bigjools.19:16
* bigjools waves back19:16
kikoBjornT, question for you: does mthaddon know that we did a CB yesterday?19:16
mthaddonI do, yes19:16
Rinchen[TOPIC] New packages required (salgado)19:17
MootBotNew Topic:  New packages required (salgado)19:17
herbkiko, BjornT I sent an email to losas yesterday after the CB19:17
salgadoif any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP.19:17
Rinchenjtv, hows that xmlproc code change coming?19:17
jtvRinchen: I was just trying to squeeze it into PQM, thanks19:17
* Rinchen wants to know when he can unpin that package19:17
kikoherb, one concern I have is that BjornT hasn't landed the fix on RF yet?19:17
Rinchenjtv, awesome, thanks.19:17
BjornTkiko: i haven't?19:18
mthaddonkiko, I think it's in process, or landing...19:18
kikoBjornT, okay, need to refresh that mailbox then :)19:18
BjornTkiko: r615119:18
Rinchen[TOPIC] A top user-affecting issue (mrevell)19:18
MootBotNew Topic:  A top user-affecting issue (mrevell)19:18
mrevell Happy Hardy release day!19:18
mrevellThe user-affecting issue I'd like to highlight today is that impact that interest in the new Ubuntu release appears to have had on sites that rely on Launchpad for authentication.19:18
mrevell I know this happens only twice a year but I'd like to acknowledge the slow-down in a post to lp-users and explain its cause. Is there some good news I can offer in that message?19:18
BjornTkiko: i had to resubmit it, since the first one failed due to a spurious test failure...19:19
kikoBjornT, known spurious test failure? :)19:19
SteveAmrevell: the cause is some old software written when launchpad and ubuntu had far fewer users19:19
SteveAmrevell: the good news is that we're replacing it with new software that works much better19:19
mrevellthanks SteveA :)19:20
SteveAso this will be the last such slow-down19:20
mrevellgreat to hear, thanks for that.19:20
mrevellThanks Rinchen19:20
Rinchen[TOPIC] Doc Team report (mrevell)19:20
MootBotNew Topic:  Doc Team report (mrevell)19:20
mrevellThis week please give me your feedback on the proposed tour layouts. I've posted new drafts to the list today.19:20
mrevellI know not everyone is directly interested in this sort of thing but I'm interested in everyone's view.19:21
Rinchenmrevell, has the community members of the doc team been active lately?19:21
mrevellRinchen: We haven't had much interest lately and I need to restoke interest after our 1.2.4 release (i.e. when I'm clear to do that)19:22
mrevells/clear/more free19:22
Rinchenok, thanks19:22
mrevellI'd also be grateful if you could give a few moments thought on the podcast idea.19:22
mrevellthanks Rinchen19:22
Rinchen[TOPIC] Community procedure for unplanned downtime (mpt)19:22
MootBotNew Topic:  Community procedure for unplanned downtime (mpt)19:22
kikomrevell, I really like the new tour layouts, btw19:22
mptLast Sunday, Launchpad had major availability problems for an extended period19:22
mrevellkiko: That's great to hear. If you have any specific feedback I'll give it to Gavin in my call with him tomorrow19:23
mptThere were non-Canonical people in #launchpad who noticed, but they didn't know what to do.19:23
mptI started a mailing list thread about this on Sunday, but it hasn't come to any conclusion19:23
kikomrevell, I'll try getting email before I trvel19:23
mrevellthanks kiko19:23
mptSo we still need to decide:19:23
mpt* Is it necessary for us to publish some way of getting in touch with admins when Launchpad is down?19:24
mpt- If so, what should that be?19:24
mpt- And if not, how will we prevent such downtime happening in future?19:24
stubIs there anyone in Montreal accessible by our users?19:24
kikompt, when we were down, what happened when loading the site?19:24
mrevellmpt: Presumably help.lp.net was down as well?19:24
gmbkiko: HTTP Timeouts19:24
SteveAkiko: basically, the site was totally unresponsive19:24
SteveAnot even a 503 page19:24
kikozaz a bummer19:25
SteveAor 50x page19:25
mptkiko, as I understand it, pages were *occasionally* available, but extremely slowly if at all.19:25
kikoput something on the #launchpad topic19:25
SteveAit was caused by the problem we just fixed19:25
kikoor on help.launchpad.net19:25
SteveAor are about to fix19:25
mptkiko, who are you suggesting do this?19:25
SteveAhowever, I don't think we need to set up anything special about this19:25
mrevellIs there anything fancy we can do DNS-wise that would redirect people to an off-site holding page in the case of this sort of outage?19:25
SteveAmrevell: no19:25
kikompt, well, that's my questions for you19:26
SteveAthe issue is this19:26
kikoI'm not suggesting much19:26
SteveAwe have monitoring systems19:26
kikothink it's a bit of a non-issue19:26
SteveAand they tell us when launchpad is not functioning19:26
mptkiko, people in #launchpad did change the /topic, but that's all they *could* do.19:26
SteveAon Sunday, no one was available to respond to the monitoring systems19:26
kikompt, I mean put in the /topic "call 1800LAUNCHPAD" etc19:26
SteveAthe solution is that we have people available to respond to the monitoring systems19:26
SteveAand I'm talking to the information systems people in Canonical about that.19:27
SteveAthe monitoring systems detected the outage at the same time that people on the channel did.19:27
RinchenAs a normal user, if the service went down, I'd like the warm fuzzies to know someone was looking at it.  I believe we should have weekend response to monitoring alerts.19:28
RinchenI would also be very thankful if someone posted a time when they think the problem might be fixed19:28
Rinchen(as a normal user)19:28
matsubaraRinchen: perhaps we should add that to the DealingwithCrisis policy/doc19:28
kikoRinchen, posted /where/?19:28
SteveARinchen: if the monitoring system had been responded to on Sunday, the problem would have been fixed within 5 mins.19:29
Rinchenkiko, dunno. Somewhere where I would naturally see it.19:29
kikothe issue as I see it is that the site is down and there's no fallback place to look19:29
matsubaraRinchen: I mean, we should add that the part of the procedure is to notify in public places that people are looking at the issue19:29
Rinchenkiko, right19:29
kikoRinchen, that's the key problem, so unless we can answer that, all bets are off19:29
Rinchenkiko, that rarely happens though19:29
SteveAstop, please19:29
SteveAwe're talking about a problem that was fixed within minutes of an appropriate person looking into it19:29
mptSteveA, will you post to launchpad@ when your discussions with IS have a conclusion?19:29
SteveAthe issue was the lack of appropriate people on that sunday19:30
SteveAand I'm talking with people about how we address that.19:30
SteveAenough with 1800LAUNCHPAD ;-)19:30
kikoSteveA, it was a non-proposal, in case you missed that :)19:30
RinchenI have more to say about this but I won't now.  Moving on...19:31
mptWe have UI for planned extended downtime. We don't have UI for unplanned extended downtime, but we may not need it.19:31
RinchenSteveA, if you could post the results of that IS discussion please as mpt suggested19:31
Rinchenthanks SteveA19:31
mptthanks SteveA19:31
Rinchenmpt, ok to move on?19:31
Rinchen[TOPIC] kiko on vacation (Kiko)19:31
MootBotNew Topic:  kiko on vacation (Kiko)19:31
kikoah, right.19:32
Rinchensomeone call guiness19:32
kikoI'm on vacation tomorrow through tuesday19:32
kikoyou can call me and I might have phone coverage19:32
kikobut look to steve and joey for RCs19:32
stub2 days!19:32
mthaddonRinchen, to order beer, or break a record?19:32
kikoI've looked at the PQM queue19:32
Rinchenmthaddon, in this case, both :-)19:32
kikoand there doesn't seem to be much at risk there19:32
kikodoes anyone have a high-risk, important or otherwise urgent landing that can't miss this rollout?19:32
RinchenI'd like to remind folks to clear out the pending-reviews queue if you haven't already19:32
* mthaddon calls guinness19:33
Rinchenbesides flacoste19:33
bigjoolskiko: yes, I am waiting for flacoste to land his restricted librarian stuff so I can land my P3A stuff19:33
kikoand his libby patch for julian19:33
kikoso I hear19:33
Rinchensilence. that's a good thing I think19:34
Rinchenthanks kiko19:34
kikoyou didn't speak19:34
kikoso I won't make any exception for your branch!19:34
Rinchener right. mrevell where's what's new? :-)19:35
* Rinchen laughs.19:35
mrevellRinchen: Need to speak to you about that.19:35
Rinchensure, let's do it right after this if you can19:35
Rinchenthanks all19:35
RinchenThank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.19:35
mrevellyep, np19:35
MootBotMeeting finished at 20:35.19:35
barryRinchen: thanks!19:35
SteveAthanks Rinchen !19:35
carlosthis one was fast!19:35
kikothanks thanks19:35
intellectronicathanks Rinchen19:35
jtvWe're early!19:35
Rinchenwe're setting records here bub19:35
carlosthanks !19:35
Rinchenmore meat, less fat19:36
bigjoolscall Guinness again19:36
=== salgado is now known as salgado-afk

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