[16:02] <danilos> me
[16:02] <Ursinha> #startmeeting
[16:02] <MootBot> Meeting started at 11:02. The chair is Ursinha.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <Ursinha> Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.
[16:02] <Ursinha> no need to rush boss :)
[16:02] <Ursinha> me
[16:02] <allenap> me
[16:02] <sinzui> me
[16:02] <Ursinha> hehe
[16:02] <rockstar> I know, danilos is being a suckup
[16:02] <rockstar> me
[16:02] <matsubara> me
[16:02] <danilos> me again ;)
[16:03] <Ursinha> ok, so matsubara is in behalf of foundations and bigjools is half-here
[16:03] <danilos> rockstar, I'd use an \[ agreed\] on that :)
[16:03] <matsubara> Chex, hi
[16:04] <Ursinha> stub isn't here, so
[16:04] <danilos> half of bigjools is more than enough for anybody
[16:04] <Chex> matsubara: hello
[16:04] <matsubara> stub is excused from the meetings due to the time
[16:04] <Ursinha> [action] send email to stub about the dba report
[16:04] <MootBot> ACTION received:  send email to stub about the dba report
[16:04] <Ursinha> matsubara: that's ok, I'll add a note in the MeetingAgenda page
[16:04] <Ursinha> so, we're all here
[16:04] <Ursinha> [TOPIC] Agenda * Actions from last meeting * Oops report & Critical Bugs & Broken scripts * Operations report (mthaddon/Chex/spm/mbarnett) * DBA report (stub) * Proposed items
[16:04] <MootBot> New Topic:  Agenda * Actions from last meeting * Oops report & Critical Bugs & Broken scripts * Operations report (mthaddon/Chex/spm/mbarnett) * DBA report (stub) * Proposed items
[16:05] <Ursinha> sigh
[16:05] <Ursinha> well, you got the idea :)
[16:05] <Ursinha> [TOPIC] * Actions from last meeting
[16:05] <MootBot> New Topic:  * Actions from last meeting
[16:05] <Ursinha>     * matsubara and/or Ursinha to add a count of untriaged bugs per team to the oops section
[16:05] <Ursinha>       * Done, I have them here :)
[16:05] <Ursinha>      * Chex to verify why oops-pruner is failing and reply to the failure email with more information.
[16:05] <Ursinha>       * This was fixed: spm removed checking from gangotri and added to wampee and soybean
[16:06] <Ursinha>      * sinzui to work with losas to set the increase threshold for the product release finder monitoring script.
[16:06] <sinzui> Not done. I will follow up today
[16:06] <matsubara> oops-pruner action item was sorted out
[16:06] <Ursinha> matsubara: I've added a note there :)
[16:06] <Ursinha> thanks ubottu
[16:06] <Ursinha> thanks sinzui
[16:06] <matsubara> oops, missed that :-)
[16:06] <Ursinha> [action] sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script
[16:06] <MootBot> ACTION received:  sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script
[16:06] <Ursinha> matsubara: :)
[16:07] <Ursinha> next!
[16:07] <Ursinha> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[16:07] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[16:07] <Ursinha> only one bug, bug 535071
[16:07] <Ursinha> matsubara: I only would like to ask if there's hope to fix this this cycle
[16:08] <Ursinha> matsubara: now that the LocationError bug is fixed, this is the next in the oops rank
[16:08] <matsubara> Ursinha, not sure, I'll bring it up with Gary to have it scheduled
[16:08] <Ursinha> (for reference: LocationError bug is bug 538207)
[16:08] <Ursinha> thanks matsubara
[16:09] <Ursinha> [action] matsubara to talk to gary_poster about bug 535071
[16:09] <MootBot> ACTION received:  matsubara to talk to gary_poster about bug 535071
[16:09] <matsubara> [action] matsubara to talk to Gary about scheduling bug 535071
[16:09] <Ursinha> all critical bugs are fix committed
[16:09] <matsubara> great, thanks Ursinha
[16:09] <Ursinha> and
[16:09] <Ursinha> I see that librarian-gc failed on 16, but haven't seen any other failures, will keep an eye
[16:09] <Ursinha> matsubara: any failing scripts I'm missing?
[16:10] <matsubara> nope, we already have an action item for prf
[16:10] <Ursinha> great, next!
[16:10] <Ursinha> will talk about the untriaged bugs in the Proposed items section
[16:10] <Ursinha> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
[16:10] <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
[16:10] <rockstar> Ursinha, you didn't bring up my critical bug...
[16:11] <Ursinha> rockstar: hmm I right before the meeting all critical bugs were fix committed...
[16:11] <Ursinha> s/I right/right/
[16:11] <Ursinha> rockstar: hmm they are, which one is your critical bug?
[16:12] <rockstar> Ursinha, oh, well, yeah, it's fix committed, but a critical bug wouldn't be done 'til fix released (I'd figure)
[16:13] <Ursinha> rockstar: well, I always assumed that having it fixed, the devel would make it to the end.. are you having issues to have your fix cherrypicked?
[16:14] <rockstar> Ursinha, no, but I was just prepared to give my statement.  If you don't need it, I'll shut up.  :)
[16:14] <Ursinha> rockstar: c'mon :)
[16:15] <Ursinha> rockstar: go ahead, please
[16:16] <Ursinha> rockstar: ok ok
[16:16] <Ursinha> :)
[16:16] <Ursinha> Chex: hi :) stage is yours
[16:17]  * rockstar apologizes for interruption
[16:18] <Chex> hello everyone
[16:18] <Chex> here is the LOSA report for this week, a bit brief:
[16:18]  * bigjools reads  scrollback and throws wet fish at danilos
[16:19] <Chex> - LP Memory Leaks:  We have gone through a couple rounds of testing trying to track down these appserver memory leaks.
[16:19] <Chex>   (Bug #531071)
[16:20] <Chex> - Codebrowse crashes: We have a new debugging procedure to capture the python crashdump for now, we are
[16:21] <Chex>   waiting for GDB debugger syntax give better crash info to the developers.
[16:21] <Chex> - LP incidents of note: ; LP Cherry-picks:
[16:21] <Chex>           16-Mar: CP 9091 to lpnet*
[16:22] <Chex>           18-Mar: CP 9093 to librarian2
[16:23] <Chex> and thats it for this week. any comments/questions??
[16:23] <Ursinha> I'm fine, anyone else?
[16:23] <danilos> Chex, nice, is there any process in place to escalate those crashes?
[16:25] <danilos> ok, I guess that's a no :)
[16:25] <danilos> or I am offline :)
[16:25] <Ursinha> danilos: you're not
[16:25] <Ursinha> or we're both on a parallel universe
[16:25] <Chex> danilos: not really, right now michael hudson asked us to trigger a coredump, and let me know where the file is, for now, and he will work on a GDB way of tracing
[16:26] <danilos> Chex, cool, so it's basically a per-request basis, right? iow it won't happen automatically when we get crashes
[16:27] <Chex> danilos: thats correct, he asked us to do this for now: ' gcore $loggerhead_pid '
[16:27] <danilos> Chex, ok, thanks a lot, very useful to know if we ever come to need it (though, hopefully not)
[16:28] <Chex> danilos: yes sure. welcome
[16:28] <Ursinha> anything else?
[16:28] <Ursinha> I'll take that as a no :)
[16:28] <Ursinha> moving on
[16:28] <Ursinha> [TOPIC] * DBA report (stub)
[16:28] <MootBot> New Topic:  * DBA report (stub)
[16:29] <Ursinha> stub is excused, I have an action for getting the report
[16:29] <Ursinha> next!
[16:29] <Ursinha> [TOPIC] * Proposed items
[16:29] <MootBot> New Topic:  * Proposed items
[16:29] <Ursinha> I have a few :)
[16:29] <Ursinha>  * qa tagging: NEW! launchpad queries and "qa summary"
[16:29] <Ursinha>  * untriaged bugs and QA stats of the week
[16:29] <Ursinha>  * Feedback on the new process, improvement suggestions and comments welcome :)
[16:30] <Ursinha> ok, so the first one
[16:30] <Ursinha> I've created a list of queries to make qa life easier: https://dev.launchpad.net/PolicyAndProcess/PreReleaseQAProcess/Experiment/QueryList
[16:30] <Ursinha> have sent them to the dev list, but I want to make sure you're not in unnecessary pain
[16:30] <Ursinha> :)
[16:30] <Ursinha> there are queries per devel and tag, so it's easy to find a list in lp for a person
[16:30] <Ursinha> but I see this is not enough, team leads need team overall and we can't have it using launchpad UI
[16:30] <Ursinha> so I created a "qa summary" for each team, you can find yours here: https://devpad.canonical.com/~lpqateam/testplans/
[16:31] <Ursinha> I've filed a RT to have these synced to rookery, to be accessible to public
[16:31] <Ursinha> questions?
[16:32] <danilos> we should email all the TLs about these!
[16:33]  * Ursinha adds to her notebook
[16:33] <Ursinha> [action] Ursinha to send email to TLs about QA summaries
[16:33] <MootBot> ACTION received:  Ursinha to send email to TLs about QA summaries
[16:33] <sinzui> I just add the qa urls to the milestone page.
[16:33] <Ursinha> sinzui: is that helpful?
[16:34] <danilos> sinzui, the problem is that we can't search by all the persons in a team, so if someone has done work outside your core app, it's hard to see it
[16:34] <Ursinha> danilos: exactly
[16:34] <Ursinha> team != lp project
[16:34] <sinzui> Anyone from my team or user can see the bugs we ware working and and see our QA status. Since we do not necessarily QA our own landings, I do not care about which person has the tag. I care about the team
[16:35] <rockstar> Ursinha, code team's summary is blank.
[16:35] <Ursinha> rockstar: it's because it's being generated now
[16:35] <Ursinha> (really)
[16:35] <Ursinha> every 15 minutes
[16:35] <rockstar> Ursinha, oh, I assumed it was because we were awesome.
[16:35] <Ursinha> lol
[16:35] <danilos> sinzui, right, and malone doesn't offer the option to search per-team, only per-application or per single person
[16:36] <Ursinha> danilos: sinzui, bug 520569
[16:36] <sinzui> Ursinha: yes, but when anyone fixes a bug in registry, I wan that report because my team is responsible for the app. If a contributor lands something bad in the registry project, it is not the contributor ot the QA members who fix it; the registry team fixes it
[16:37] <danilos> sinzui, right, but sometimes people from your team will land stuff in... launchpad-web project
[16:37] <danilos> sinzui, and who'll ensure that QA happens there?
[16:37] <Ursinha> sinzui: thanks for explaining your case
[16:37] <sinzui> I search launchpad-project too
[16:37] <sinzui> tags work for project
[16:38] <danilos> sinzui, this report should give you a smaller list to go through instead of going through launchpad-project, and we can have RM worry about launchpad-project
[16:38] <danilos> sinzui, nobody will mind if you always worry about launchpad-project :)
[16:38] <danilos> I still think this is a useful list to have
[16:38] <danilos> if that's what we are arguing
[16:38] <Ursinha> :)
[16:39] <Ursinha> I'm not sure I got the idea, but if sinzui needs a list of lp-registry items, it's easy to have it using Launchpad ui
[16:39] <sinzui> I do not need a list.
[16:39] <Ursinha> if that's what we are arguing :P
[16:40] <Ursinha> sinzui: are you happy with the things you have today?
[16:42] <sinzui> No, but that is because I think I want to build a way to find the intersection of a team with a project or series or milestone to get a report of bugs and blueprints
[16:42] <danilos> Ursinha, sinzui: let's move on, and we can discuss the merits of this on the list, and suggest improvements as well; Ursinha, what's the LP project to file bugs/wishes against?
[16:43] <Ursinha> sinzui: if I add a list of launchpad-registry to that list, would help?
[16:43] <sinzui> There is still a problem that no report understands that I and a canonical hacker and a contributor. My team is not responsible for QAing what I contribute
[16:43] <Ursinha> danilos: it's lp-qa-tools
[16:43] <sinzui> s/I and a/I am a/
[16:43] <Ursinha> sinzui: in general those items fall in the launchpad itself team, and me and matsubara take care of that
[16:43] <danilos> sinzui, well, you are responsible for that, and LP team is responsible for not letting unQAd items through, so we'd either have to back it out or QA it
[16:44] <danilos> sinzui, at least IMHO, but it's a different topic, so let's not discuss it now :)
[16:44] <sinzui> You have never QAed my contributions to blueprints, answers, or foundations
[16:45] <Ursinha> sinzui, danilos, I'll send the email to the list, and we can discuss the details in there, what about that?
[16:45] <danilos> sinzui, that's because we've done a bad job with QA in general
[16:45] <sinzui> And I do QA all contributors work who land something in blueprints, answers or registry.
[16:46] <danilos> sinzui, that's very nice, and nobody is questioning that; whether we should rely on sinzui to QA all the items like that is an open question with a very simple answer ("no, we all should do it or help community do it")
[16:47] <danilos> anywaay, let's move on
[16:48] <Ursinha> ok
[16:48] <Ursinha> thanks danilos and sinzui for speaking up
[16:48] <Ursinha> :)
[16:48] <Ursinha> list of untriaged bugs in launchpad-project, a picture of a moment before the meeting: http://paste.ubuntu.com/397314/
[16:48] <danilos> thanks
[16:48] <Ursinha> or

[16:49] <Ursinha> Soyuz (soyuz): 79
[16:49] <Ursinha> launchpadlib  (launchpadlib): 25
[16:49] <Ursinha> OOPS Tools (oops-tools): 22
[16:49] <Ursinha> Launchpad Developer Utilities (lp-dev-utils): 9
[16:49] <Ursinha> Launchpad QA Utilities (lp-qa-tools): 7
[16:49] <Ursinha> Launchpad Development Wiki Moin theme (launchpad-dev-moin-theme): 6
[16:49] <Ursinha> Launchpad Bugs (malone): 5
[16:49] <Ursinha> Launchpad Auto Build System (launchpad-buildd): 4
[16:49] <Ursinha> Launchpad Help Wiki Moin theme (launchpad-help-moin-theme): 4
[16:49] <Ursinha> launchpad-web (launchpad-web): 3
[16:49] <Ursinha> Launchpad Translations (rosetta): 3
[16:49] <Ursinha> Launchpad CSCVS (launchpad-cscvs): 2
[16:49] <Ursinha> launchpad-loggerhead (launchpad-loggerhead): 2
[16:49] <danilos> bigjools, do you think soyuz will need any help in triaging?
[16:49] <Ursinha> Launchpad News WordPress Theme (launchpad-news-wordpress-theme): 2
[16:49] <Ursinha> Launchpad Buildbot Configuration (lpbuildbot): 2
[16:49] <Ursinha> trac-launchpad-migrator (trac-launchpad-migrator): 2
[16:49] <Ursinha> Launchpad Documentation (launchpad-documentation): 1

[16:49] <bigjools> if you think you can help, yes please
[16:50] <bigjools> if it's obvious what to do, do it (but let me know)
[16:50] <danilos> bigjools, I'll go 'invalidate' a dozen or so, just to give a hand
[16:50] <bigjools> bug fixing for dummies
[16:50] <Ursinha> danilos: I have a script that does that.... kidding
[16:50] <Ursinha> :P
[16:50] <matsubara> I'll take care of the 22 New items for oops-tools
[16:50] <danilos> bigjools, and I'll mark a bunch of others as 'incomplete' with a comment "Why do you think it is so?"
[16:50] <matsubara> [action] matsubara to triage open oops-tools bugs
[16:51] <rockstar> Fail. launchpad-code isn't in that list.
[16:51] <danilos> rockstar, this time it probably means you are amazing
[16:51] <matsubara> that's because you have 0 new oopses
[16:51] <matsubara> rockstar, good job!
[16:51] <matsubara> :-)
[16:51] <rockstar> daniloff, yeah, I was fishing...
[16:51] <rockstar> :)
[16:51] <matsubara> s/oopses/bugs/
[16:51] <Ursinha> rockstar: because it has no new bugs
[16:51] <Ursinha> you are all so funny today :)
[16:51] <Ursinha> [action] matsubara to triage open oops-tools bugs
[16:51] <MootBot> ACTION received:  matsubara to triage open oops-tools bugs
[16:52] <rockstar> Ursinha, looks aren't everything though
[16:52] <Ursinha> [action] Ursinha to triage open lp-qa-tools bugs
[16:52] <MootBot> ACTION received:  Ursinha to triage open lp-qa-tools bugs
[16:53] <Ursinha> rockstar: sorry? :)
[16:53] <rockstar> Ursinha, <Ursinha> you are all so funny today :)
[16:54] <Ursinha> anyway, matsubara and I want to reactivate a section in this meeting, QA stats of the week
[16:54] <Ursinha> then we can discuss the status of bug triage and QA
[16:55] <Ursinha> that's all from me, I'm done here
[16:55] <Ursinha> anyone willing to add something?
[16:56] <Ursinha> ok, so sorry for taking so long
[16:56] <Ursinha> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
[16:56] <Ursinha> #endmeeting
[16:56] <MootBot> Meeting finished at 11:56.
[16:56] <Ursinha> thanks everyone