[17:00] <danilos> me?
[17:01] <matsubara> moo
[17:01] <danilos> yoo
[17:01] <Ursinha> hahaha
[17:01] <matsubara> oinc
[17:01] <matsubara> farmiville meets launchpad
[17:02]  * rockstar  
[17:02] <gary_poster> me
[17:02] <sinzui> me
[17:02] <Ursinha> argh
[17:02] <Ursinha> #startmeeting
[17:02] <MootBot> Meeting started at 11:02. The chair is Ursinha.
[17:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:02] <sinzui> me
[17:02] <Ursinha> sigh
[17:02] <matsubara> me
[17:02] <Ursinha> [TOPIC] Roll Call
[17:02] <Ursinha> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!
[17:02] <MootBot> New Topic:  Roll Call
[17:02] <sinzui> me
[17:02] <Ursinha> meeeeee
[17:02] <Chex> me
[17:02] <matsubara> me
[17:02] <Ursinha> sinzui is here several times
[17:03] <Ursinha> bigjools,
[17:03] <Ursinha> hi
[17:03]  * bigjools excuses himself from the meeting
[17:03] <bigjools> UDS...
[17:03] <Ursinha> I guess we don't have a bugs' person here
[17:03] <Ursinha> bigjools, I  have one question for you in the oops section, should be easy for you :)
[17:04] <Ursinha> ok
[17:04] <Ursinha> [TOPIC] Agenda
[17:04] <Ursinha>  * Actions from last meeting
[17:04] <Ursinha>  * Oops report & Critical Bugs & Broken scripts
[17:04] <Ursinha>  * Operations report (mthaddon/Chex/spm/mbarnett)
[17:04] <Ursinha>  * DBA report (stub)
[17:04] <MootBot> New Topic:  Agenda
[17:04] <Ursinha>  * QA stats of the week
[17:04] <Ursinha>  * Proposed items
[17:04] <Ursinha> [TOPIC] * Actions from last meeting
[17:04] <MootBot> New Topic:  * Actions from last meeting
[17:04] <Ursinha>     * Ursinha to triage lp-qa-tools bugs
[17:04] <Ursinha>        * done.
[17:04] <Ursinha>     * matsubara to talk to foundations about OOPS-1585G1243
[17:04] <Ursinha>         * Talked to Gary about it and filed https://launchpad.net/bugs/579987
[17:04] <Ursinha>     * adeuring to follow up on calculate_bug_heat script failure
[17:04] <Ursinha>     * matsubara to chase landing for bug 574493
[17:04] <Ursinha>         * Landed and CP'ed
[17:04] <Ursinha>     * matsubara to chase landing for bug 575426
[17:04] <Ursinha>         * Landed and CP'ed
[17:04] <Ursinha>     * matsubara to ask for the DBA report
[17:04] <Ursinha>         * emailed stub asking for it
[17:04] <Ursinha>     * all QA contacts to take orphaned commits' lists to their teams to check if were left untested items behind because they were orphaned commits
[17:04] <Ursinha> bot is sleeping
[17:04] <Ursinha> my stuff is ok, so is matsubara's
[17:05] <Ursinha> adeuring is not here to follow up on his item
[17:05] <Ursinha> [action] Ursinha to chase adeuring abour calculate_bug_heat failing script
[17:05] <MootBot> ACTION received:  Ursinha to chase adeuring abour calculate_bug_heat failing script
[17:05] <Ursinha> about the orphaned commits, we can discuss that in the QA section
[17:06] <Ursinha> moving on
[17:06] <Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[17:06] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[17:06] <Ursinha> One bug and one oops for code team, and one oops to soyuz
[17:06] <Ursinha> the code bug is bug 579004, triaged high and targetted to 10.05, seems to affect only staging
[17:06] <Ursinha> fine
[17:06] <Ursinha> the oops: rockstar, any ideas? https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1593S580
[17:06] <Ursinha> https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1593EC1021, NotOneError seems to be bug 523346, already fix released, but I still see that happening
[17:06] <Ursinha> bigjools, is that the same thing? ^
[17:07] <bigjools> Ursinha: gah
[17:07] <rockstar> Ursinha, I'll file a bug.
[17:07] <bigjools> it's related
[17:08] <Ursinha> thanks rockstar
[17:08] <Ursinha> bigjools, may I file another bug?
[17:08] <bigjools> Ursinha: yes please, and mention that other one
[17:08] <Ursinha> bigjools, sure
[17:08] <bigjools> thanks
[17:08] <Ursinha> [action] Ursinha to file a bug for OOPS-1593EC1021, related to bug 523346
[17:08] <MootBot> ACTION received:  Ursinha to file a bug for OOPS-1593EC1021, related to bug 523346
[17:09] <Ursinha> thanks rockstar and bigjools, I love you both
[17:09] <Ursinha> moving on
[17:09] <Ursinha> calculate_bug_heat and upgrade_branches were the last scripts to fail
[17:09] <Ursinha> rockstar, do you know about the upgrade_branches? is that related to code as it seems?
[17:09] <bigjools> heh :)
[17:09] <rockstar> Ursinha, yes.  That script is my baby.
[17:09] <Ursinha> rockstar, oh, it seems it's been crying on his last runs
[17:10] <Ursinha> or its :)
[17:10] <rockstar> Ursinha, I'll look into it.
[17:10] <Ursinha> thanks rockstar
[17:10] <Ursinha> much appreciated
[17:10] <rockstar> Ursinha, the conjugated form was correct, since it's a conjugation of "it" and "has"
[17:10] <Ursinha> [action] rockstar to look into upgrade_branches failures
[17:10] <MootBot> ACTION received:  rockstar to look into upgrade_branches failures
[17:10] <Ursinha> rockstar, I was referring to s/his/its/ ;)
[17:10] <Ursinha> s/;)/:)
[17:11] <Ursinha> thanks :)
[17:11] <Ursinha> we have three critical bugs, two already fix committed: bug 574142 and bug 574493
[17:11] <Ursinha> gary_poster, sinzui, are those two going to be or were CPed?
[17:11] <Ursinha> there's one in progress, code, bug 578331, last comment was danilos'
[17:11] <Ursinha> how is that?
[17:11] <mwhudson> i think it's fix committed now?
[17:11] <danilos> Ursinha, it's on production-stable, needs CPing
[17:12] <Ursinha> oh, so mwhudson is here
[17:12] <mwhudson> oops
[17:12] <Ursinha> camper :)
[17:12] <mwhudson> my cover is busted
[17:12] <danilos> https://lpbuildbot.canonical.com/builders/prod_lp/builds/62
[17:12] <sinzui> Ursinha, it is fix released, I updated it
[17:12] <sinzui> now
[17:12] <gary_poster> Ursinha, I'm remebering only one critical and it has been CP'd--the log-out one
[17:12] <Ursinha> thanks sinzui
[17:12] <Ursinha> gary_poster, that one seems private, let me see
[17:13] <matsubara> Ursinha, 574493 was CP'ed
[17:13] <gary_poster> bug 574493, right?
[17:13] <gary_poster> that's CP'd
[17:13] <Ursinha> gary_poster, yes
[17:13] <gary_poster> cool
[17:13] <Ursinha> matsubara, gary_poster, so, it's fix released :) could you mark it as such, please?
[17:13] <Ursinha> or I can do that :)
[17:13] <gary_poster> will do
[17:13] <Ursinha> thank you
[17:14] <Ursinha> danilos, are you taking care of that CP?
[17:15] <matsubara> I didn't mark as fix released before because of gary's comment saying the fix was CP'd but not landed on devel. I was waiting for it to reach devel a go through the usual process
[17:15] <matsubara> s/a/and/
[17:15] <danilos> Ursinha, will do
[17:15] <gary_poster> matsubara, ack.  It happened early this morning
[17:15] <Ursinha> matsubara, that's ok, I was just wondering if they could be closed now
[17:15] <Ursinha> danilos, thanks
[17:15] <Ursinha> [action] danilos to take care of CPing bug 578331 fix
[17:15] <MootBot> ACTION received:  danilos to take care of CPing bug 578331 fix
[17:16] <Ursinha> good
[17:16] <Ursinha> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
[17:16] <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
[17:16] <Ursinha> Chex, stage is all yours
[17:16] <Chex> hello everyone, here is this weeks LOSA report:
[17:16] <Chex> - Applied LP security fix for Bug# 578914
[17:16] <Chex>         : Rolled out in security mode, applying CP's to codebrowse & codehost, and cowboy edge.
[17:16] <Chex> - Bug 531071: app servers leaking memory
[17:16] <Chex>         : We have a few dump-logs now ( LPIncidentLog ) , has anyone looked at or could look at these to debug the issues here?
[17:16] <Chex>  - LP incidents of note: : Codebrowse fixed from hourly restarts after last week rollout, but still needs restarting, daily, or more. : ftp/poppy service crashed a few times this week, Bug 414482
[17:17] <Chex>         : Apr-11: CP 9339 App Servers & codehost/crowberry
[17:17] <Chex>         : Apr-12: CP 9341 to germanium/cocoplum
[17:17] <Chex>         : Apr-12: CP 9342 to lpnet/cocoplum & loganberry-bzrsyncd
[17:18] <Chex> questions/comments on the report?
[17:18] <danilos> I guess that's May, or an abbreviation for something like "Anonymous Public Report" :)
[17:18] <Chex> wow, yes sorry
[17:18] <Chex> .. s/Apr/May/ my mistake.
[17:18] <danilos> Chex, should we try to get bigjools to up the priority on poppy bug?
[17:19] <danilos> Chex, if that's bigjools territory at all?
[17:19] <bigjools> it is
[17:19] <bigjools> but it's a bug in zope
[17:19] <bigjools> so we're working around that by writing a new sftp server :)
[17:20] <Ursinha> what a workaround :)
[17:20] <danilos> woohoo, simple workarounds :)
[17:20] <gary_poster> probably late for this, but I'm always happy to try and apply pressure withing Zope community if necessary
[17:21] <bigjools> good to know, thanks
[17:21] <Ursinha> ok, anyone else?
[17:22] <Ursinha> bug 531071 maybe?
[17:22] <Ursinha> gary_poster, ^
[17:22] <Ursinha> this is already targeted to 10.04
[17:22] <gary_poster> we now have some meliae outputs as of the past week.  I'll be investigating them soon.
[17:22] <Chex> Ursinha: gary_poster: we have crash dumps of what was requested now on the app servers, if we can work with someone who wants to look at this
[17:23] <Ursinha> s/already/still/
[17:23] <Chex> gary_poster: ah fair enough, thank you
[17:23] <gary_poster> Chex: (I assume they are the same ones you are talking about--spm sent us some emails)
[17:23] <Ursinha> gary_poster, may I target that to this cycle?
[17:24] <Chex> gary_poster: yes I think so, what I saw in the incident logs was in spm
[17:24] <Chex> 's timeframe, so.
[17:24] <gary_poster> Chex: cool
[17:24] <gary_poster> Ursinha: too late ;-) but thanks
[17:24] <Ursinha> haha, thanks gary_poster :)
[17:24] <Ursinha> moving on then :)
[17:24] <Ursinha> [TOPIC] * DBA report (stub)
[17:24] <Ursinha> [action] send email to stub about the dba report of the week
[17:24] <MootBot> New Topic:  * DBA report (stub)
[17:24] <MootBot> ACTION received:  send email to stub about the dba report of the week
[17:24] <Ursinha> [TOPIC] * QA stats of the week
[17:24] <MootBot> New Topic:  * QA stats of the week
[17:24] <Ursinha> Untested items per team:
[17:24] <Ursinha> Code: 3
[17:24] <Ursinha> Foundations: 2
[17:24] <Ursinha> Registry: 0
[17:24] <Ursinha> Bugs: 3
[17:24] <Ursinha> Translations: 2
[17:24] <Ursinha> Soyuz: 3
[17:24] <Ursinha> Strategy: 0
[17:25] <gary_poster> Untested == QA?
[17:25] <gary_poster> duh
[17:25] <gary_poster> yes
[17:25] <Ursinha> :)
[17:25] <Ursinha> one thing I notice is that since we started using tags, we've been having less untested items at once
[17:25] <Ursinha> which is cool
[17:25] <Ursinha> :)
[17:26] <Ursinha> Untriaged bugs per project:
[17:26] <gary_poster> agreed
[17:26] <Ursinha> malone: 17
[17:26] <Ursinha> launchpad-buildd: 12
[17:26] <Ursinha> lp-dev-utils: 9
[17:26] <Ursinha> launchpadlib: 9
[17:26] <Ursinha> launchpad-dev-moin-theme: 6
[17:26] <Ursinha> launchpad-code: 5
[17:26] <Ursinha> launchpad-foundations: 3
[17:26] <Ursinha> soyuz: 3
[17:26] <Ursinha> launchpad-help-moin-theme: 3
[17:26] <Ursinha> lpbuildbot: 2
[17:26] <Ursinha> trac-launchpad-migrator: 2
[17:26] <Ursinha> launchpad-news-wordpress-theme: 2
[17:26] <Ursinha> launchpad-cscvs: 2
[17:26] <Ursinha> launchpad: 1
[17:26] <Ursinha> launchpad-web: 1
[17:26] <Ursinha> launchpad-loggerhead: 1
[17:26] <Ursinha> launchpad-documentation: 1
[17:26] <Ursinha> tickcount: 1
[17:27] <Ursinha> we're not that bad triaging bugs as well
[17:27] <Ursinha> about the orphaned commits
[17:28] <Ursinha> last week I asked the QA contacts to check with their teams all OCs that are yours, to see if we're leaving untested things behind
[17:28] <Ursinha> sinzui answered me, what about the others?
[17:28] <matsubara> I suck. I forgot to bring that up with my team
[17:28] <Ursinha> https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.04-devel and https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.04-db-devel
[17:29] <Ursinha> rockstar, and you?
[17:29] <rockstar> We talked about it.  I don't know if anyone did anything about it.
[17:29] <sinzui> I will bring up the branch-link-to-bug issue in the next reviewers meeting. Many contributors do not do this
[17:30] <danilos> Ursinha, I totally don't remember the discussion, which means that I suck
[17:30] <Ursinha> :)
[17:30] <sinzui> We could make ec2 land require a linked bug
[17:30] <Ursinha> c'mon people :)
[17:30] <Ursinha> sinzui, guess the problem is that not all commits really require bugs
[17:30] <rockstar> Oh no, I think we did talk about it, and determined that there were no orphaned commits.
[17:30] <wgrant> What about refactorings?
[17:30] <Ursinha> and not everyone uses ec2
[17:30] <sinzui> right
[17:30] <Ursinha> ah, hello wgrant :)
[17:30] <rockstar> However, we're also not linking bugs to branches in many cases.
[17:31] <wgrant> Ursinha: Yeah, I'm not asleep for once :P
[17:31] <sinzui> pqm submit certain is not
[17:31] <Ursinha> wgrant, :P
[17:31] <rockstar> Ursinha, we haven't really been tracking QA in the bugtracker - We've been using our Kanban board.
[17:31] <matsubara> if you use --fixes=lp:NNNN when you commit, then when you push the branch to LP, it'll be linked automatically
[17:31] <Ursinha> rockstar, I see. this is not good, but we fall again in the kanban board/lp integration
[17:31] <Ursinha> problem
[17:32] <matsubara> and the tagging script will find out which bug was fixed by that commit, even if it's not mentioned in the commit message
[17:32] <rockstar> Ursinha, well, we have two tools essentially doing the same thing.
[17:32] <Ursinha> rockstar, also what matsubara said
[17:32] <sinzui> I still use the milestone because I am tracking every registry related blueprint and bug that I may be required to land a RC for
[17:32] <danilos> Ursinha, fwiw, I've looked through the orphan commits now and there is only one by a translations dev and that one was qa-ok :)
[17:33] <Ursinha> I don't know what everyone else agrees, but I think we should maintain lp updated so when we integrate that with kanban we'll all be used to the lp dance
[17:33] <Ursinha> thanks danilos
[17:33] <sinzui> Every contributor or even developer from another team gets their in progress bugs targets to a milestone and I verify the number of fix committed is the same number as qa-ok
[17:33] <rockstar> Ursinha, asking us to keep two duplicate tools in sync manually seems crazy.
[17:34] <gary_poster> Foundations often has multiple commits as we pursue a larger bug
[17:34] <Ursinha> rockstar, but is that hard to use --fixes or link a bug to a branch?
[17:34] <sinzui> danilos, the registry orphaned commits were for contributor branches that we landed and for testfix
[17:34] <rockstar> Ursinha, no, but I don't want to create a kanban task AND a bug for something I'm about to do.
[17:34] <danilos> sinzui, I count adiroiban as a translations developer as well :)
[17:34] <rockstar> And then move them both through their own separate processes.
[17:34] <gary_poster> We also have kanban cards for our tasks
[17:34] <rockstar> I can't use --fixes if there isn't a bug...
[17:35] <Ursinha> rockstar, I thought that the whole team had agreed on using lp as qa tracker
[17:35] <sinzui> He applied to be an lp engineer. He should be counted on someone's team
[17:35] <Ursinha> did I get this wrong?
[17:35] <rockstar> Ursinha, maybe, but the code team isn't doing it that way, and we've found that the kanban board has been the tool we've preferred.
[17:35] <Ursinha> I guess that needs to be discussed then
[17:36] <rockstar> Ursinha, we get our stuff QA'd, so it's not like things are falling through the cracks, but it doesn't have great visibility.
[17:36] <Ursinha> if you're preferring another tool, we should discuss the problems
[17:36] <rockstar> Ursinha, the problem is that we have two tools...
[17:36] <gary_poster> Ursinha: do I understand correctly that you are saying that orphan commits are bad?
[17:36] <Ursinha> rockstar, imo the problem is that we don't have kanban integration
[17:36] <danilos> Ursinha, rockstar: it's a recognized problem, and flacoste promises us we'll do something about it (two tools for the same job)
[17:36] <gary_poster> because of the QA-through-LP initiative?
[17:36] <Ursinha> gary_poster, only if they are really orphaned
[17:36] <danilos> Ursinha, let's move on
[17:37] <danilos> at least that's my take on it
[17:37] <matsubara> gary_poster, not necessarily bad, we just don't want those falling through the cracks
[17:37] <Ursinha> gary_poster, in the sense that it should have been qaed and it isn't
[17:37] <Ursinha> what matsubara said
[17:37] <gary_poster> ...and if we use LP for qa then how do we know?
[17:37] <gary_poster> right
[17:37] <matsubara> if you use LP as the QA tracker, then we have tools to help remind you that some QA is needed
[17:38] <gary_poster> I think this is a matter for discussion, but maybe not here.  mailing list?
[17:38] <Ursinha> doesn't matter if it doesn't have a bug when it doesn't need to have, the problem is not having a bug when it should
[17:38] <Ursinha> agreed gary_poster
[17:38] <gary_poster> cool
[17:38] <matsubara> if you start landing OCs, then the tools can't help remind you that QA needs to be done
[17:38] <Ursinha> so, in this meantime, I'd like to ask you to once in a while take a look in the OC list
[17:39] <Ursinha> and see if any important things are missing
[17:39] <Ursinha> https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.05-devel and https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.05-db-devel this cycle
[17:39] <Ursinha> anyone else want to say something?
[17:39] <Ursinha> moving on :)
[17:39] <Ursinha> [TOPIC] * Proposed items
[17:39] <Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
[17:39] <MootBot> New Topic:  * Proposed items
[17:39] <Ursinha> #endmeeting
[17:39] <MootBot> Meeting finished at 11:39.
[17:40] <Ursinha> errrrr bad paste :)
[17:40] <Ursinha> but we didn't have any other proposed items, so, nevermind :)
[17:40] <gary_poster> :-)
[17:40] <matsubara> thanks Ursinha
[17:40] <gary_poster> thank you
[17:40] <Ursinha> thanks everyone for this week's meeting :)
[17:41] <danilos> cheers