DevelopmentMeeting20100318

Not logged in - Log In / Register

   1 13:02 <         danilos > me
   2 13:02 <         Ursinha > #startmeeting
   3 13: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.
   4 13:02 <         MootBot > Meeting started at 11:02. The chair is Ursinha.
   5 13:02 <         MootBot > Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
   6 13:02 <         Ursinha > no need to rush boss :)
   7 13:02 <         Ursinha > me
   8 13:02 <         allenap > me
   9 13:02 <          sinzui > me
  10 13:02 <         Ursinha > hehe
  11 13:02 <        rockstar > I know, danilos is being a suckup
  12 13:02 <        rockstar > me
  13 13:02 <       matsubara > me
  14 13:02 <         danilos > me again ;)
  15 13:03 <         Ursinha > ok, so matsubara is in behalf of foundations and bigjools is half-here
  16 13:03 <         danilos > rockstar, I'd use an \[ agreed\] on that :)
  17 13:03 <       matsubara > Chex, hi
  18 13:04 <         Ursinha > stub isn't here, so
  19 13:04 <         danilos > half of bigjools is more than enough for anybody
  20 13:04 <            Chex > matsubara: hello
  21 13:04 <       matsubara > stub is excused from the meetings due to the time
  22 13:04 <         Ursinha > [action] send email to stub about the dba report
  23 13:04 <         MootBot > ACTION received:  send email to stub about the dba report
  24 13:04 <         Ursinha > matsubara: that's ok, I'll add a note in the MeetingAgenda page
  25 13:04 <         Ursinha > so, we're all here
  26 13: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
  27 13: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
  28 13:05 <         Ursinha > sigh
  29 13:05 <         Ursinha > well, you got the idea :)
  30 13:05 <         Ursinha > [TOPIC] * Actions from last meeting
  31 13:05 <         MootBot > New Topic:  * Actions from last meeting
  32 13:05 <         Ursinha >     * matsubara and/or Ursinha to add a count of untriaged bugs per team to the oops section
  33 13:05 <         Ursinha >       * Done, I have them here :)
  34 13:05 <         Ursinha >      * Chex to verify why oops-pruner is failing and reply to the failure email with more information.
  35 13:05 <         Ursinha >       * This was fixed: spm removed checking from gangotri and added to wampee and soybean
  36 13:05 <          ubottu > https://lp-oops.canonical.com/oops.py/?oopsid=pruner
  37 13:06 <         Ursinha >      * sinzui to work with losas to set the increase threshold for the product release finder monitoring script.
  38 13:06 <          sinzui > Not done. I will follow up today
  39 13:06 <       matsubara > oops-pruner action item was sorted out
  40 13:06 <          ubottu > https://lp-oops.canonical.com/oops.py/?oopsid=pruner
  41 13:06 <         Ursinha > matsubara: I've added a note there :)
  42 13:06 <         Ursinha > thanks ubottu 
  43 13:06 <         Ursinha > thanks sinzui 
  44 13:06 <       matsubara > oops, missed that :-)
  45 13:06 <         Ursinha > [action] sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script
  46 13:06 <         MootBot > ACTION received:  sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script
  47 13:06 <         Ursinha > matsubara: :)
  48 13:07 <         Ursinha > next!
  49 13:07 <         Ursinha > [TOPIC] * Oops report & Critical Bugs & Broken scripts
  50 13:07 <         MootBot > New Topic:  * Oops report & Critical Bugs & Broken scripts
  51 13:07 <         Ursinha > only one bug, bug 535071
  52 13:07 <          ubottu > Launchpad bug 535071 in launchpad-foundations "Better error handling when librarian is offline" [High,Triaged] https://launchpad.net/bugs/535071
  53 13:07 <         Ursinha > matsubara: I only would like to ask if there's hope to fix this this cycle
  54 13:08 <         Ursinha > matsubara: now that the LocationError bug is fixed, this is the next in the oops rank
  55 13:08 <       matsubara > Ursinha, not sure, I'll bring it up with Gary to have it scheduled
  56 13:08 <         Ursinha > (for reference: LocationError bug is bug 538207)
  57 13:08 <         Ursinha > thanks matsubara 
  58 13:08 <          ubottu > Launchpad bug 538207 in launchpad-foundations "Oops calling view/isRedirectInhibited from non-launchpadview" [High,Fix committed] https://launchpad.net/bugs/538207
  59 13:09 <         Ursinha > [action] matsubara to talk to gary_poster about bug 535071
  60 13:09 <         MootBot > ACTION received:  matsubara to talk to gary_poster about bug 535071
  61 13:09 <       matsubara > [action] matsubara to talk to Gary about scheduling bug 535071
  62 13:09 <          ubottu > Launchpad bug 535071 in launchpad-foundations "Better error handling when librarian is offline" [High,Triaged] https://launchpad.net/bugs/535071
  63 13:09 <         Ursinha > all critical bugs are fix committed
  64 13:09 <       matsubara > great, thanks Ursinha
  65 13:09 <         Ursinha > and
  66 13:09 <         Ursinha > I see that librarian-gc failed on 16, but haven't seen any other failures, will keep an eye
  67 13:09 <         Ursinha > matsubara: any failing scripts I'm missing?
  68 13:10 <       matsubara > nope, we already have an action item for prf
  69 13:10 <         Ursinha > great, next!
  70 13:10 <         Ursinha > will talk about the untriaged bugs in the Proposed items section
  71 13:10 <         Ursinha > [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
  72 13:10 <         MootBot > New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
  73 13:10 <        rockstar > Ursinha, you didn't bring up my critical bug...
  74 13:11 <         Ursinha > rockstar: hmm I right before the meeting all critical bugs were fix committed...
  75 13:11 <         Ursinha > s/I right/right/
  76 13:11 <         Ursinha > rockstar: hmm they are, which one is your critical bug?
  77 13:12 <        rockstar > Ursinha, oh, well, yeah, it's fix committed, but a critical bug wouldn't be done 'til fix released (I'd figure)
  78 13: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?
  79 13:14 <        rockstar > Ursinha, no, but I was just prepared to give my statement.  If you don't need it, I'll shut up.  :)
  80 13:14 <         Ursinha > rockstar: c'mon :)
  81 13:15 <         Ursinha > rockstar: go ahead, please
  82 13:16 <         Ursinha > rockstar: ok ok
  83 13:16 <         Ursinha > :)
  84 13:16 <         Ursinha > Chex: hi :) stage is yours
  85 13:17  *       rockstar apologizes for interruption
  86 13:18 <            Chex > hello everyone
  87 13:18 <            Chex > here is the LOSA report for this week, a bit brief:
  88 13:18  *       bigjools reads  scrollback and throws wet fish at danilos
  89 13:19 <            Chex > - LP Memory Leaks:  We have gone through a couple rounds of testing trying to track down these appserver memory leaks.
  90 13:19 <            Chex >   (Bug #531071)
  91 13:19 <          ubottu > Launchpad bug 531071 in launchpad-foundations "lpnet app servers are leaking memory again" [High,Triaged] https://launchpad.net/bugs/531071
  92 13:20 <            Chex > - Codebrowse crashes: We have a new debugging procedure to capture the python crashdump for now, we are
  93 13:21 <            Chex >   waiting for GDB debugger syntax give better crash info to the developers.
  94 13:21 <            Chex > - LP incidents of note: ; LP Cherry-picks:
  95 13:21 <            Chex >           16-Mar: CP 9091 to lpnet*
  96 13:22 <            Chex >           18-Mar: CP 9093 to librarian2
  97 13:23 <            Chex > and thats it for this week. any comments/questions??
  98 13:23 <         Ursinha > I'm fine, anyone else?
  99 13:23 <         danilos > Chex, nice, is there any process in place to escalate those crashes?
 100 13:25 <         danilos > ok, I guess that's a no :)
 101 13:25 <         danilos > or I am offline :)
 102 13:25 <         Ursinha > danilos: you're not
 103 13:25 <         Ursinha > or we're both on a parallel universe
 104 13: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
 105 13:26 <         danilos > Chex, cool, so it's basically a per-request basis, right? iow it won't happen automatically when we get crashes
 106 13:27 <            Chex > danilos: thats correct, he asked us to do this for now: ' gcore $loggerhead_pid '
 107 13:27 <         danilos > Chex, ok, thanks a lot, very useful to know if we ever come to need it (though, hopefully not)
 108 13:28 <            Chex > danilos: yes sure. welcome
 109 13:28 <         Ursinha > anything else?
 110 13:28 <         Ursinha > I'll take that as a no :)
 111 13:28 <         Ursinha > moving on
 112 13:28 <         Ursinha > [TOPIC] * DBA report (stub)
 113 13:28 <         MootBot > New Topic:  * DBA report (stub)
 114 13:29 <         Ursinha > stub is excused, I have an action for getting the report
 115 13:29 <         Ursinha > next!
 116 13:29 <         Ursinha > [TOPIC] * Proposed items
 117 13:29 <         MootBot > New Topic:  * Proposed items
 118 13:29 <         Ursinha > I have a few :)
 119 13:29 <         Ursinha >  * qa tagging: NEW! launchpad queries and "qa summary"
 120 13:29 <         Ursinha >  * untriaged bugs and QA stats of the week
 121 13:29 <         Ursinha >  * Feedback on the new process, improvement suggestions and comments welcome :)
 122 13:30 <         Ursinha > ok, so the first one
 123 13:30 <         Ursinha > I've created a list of queries to make qa life easier: https://dev.launchpad.net/PolicyAndProcess/PreReleaseQAProcess/Experiment/QueryList
 124 13:30 <         Ursinha > have sent them to the dev list, but I want to make sure you're not in unnecessary pain
 125 13:30 <         Ursinha > :)
 126 13:30 <         Ursinha > there are queries per devel and tag, so it's easy to find a list in lp for a person
 127 13:30 <         Ursinha > but I see this is not enough, team leads need team overall and we can't have it using launchpad UI
 128 13:30 <         Ursinha > so I created a "qa summary" for each team, you can find yours here: https://devpad.canonical.com/~lpqateam/testplans/
 129 13:30 <         Ursinha > I've filed a RT to have these synced to rookery, to be accessible to public
 130 13:31 <         Ursinha > questions?
 131 13:32 <         danilos > we should email all the TLs about these!
 132 13:33  *            Ursinha  adds to her notebook
 133 13:33 <             Ursinha > [action] Ursinha to send email to TLs about QA summaries
 134 13:33 <             MootBot > ACTION received:  Ursinha to send email to TLs about QA summaries
 135 13:33 <              sinzui > I just add the qa urls to the milestone page.
 136 13:33 <             Ursinha > sinzui: is that helpful?
 137 13:34        [Nick] leonardr is now known as leonardr-lunch
 138 13: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
 139 13:34 <             Ursinha > danilos: exactly
 140 13:34 <             Ursinha > team != lp project
 141 13: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
 142 13:35 <            rockstar > Ursinha, code team's summary is blank.
 143 13:35 <             Ursinha > rockstar: it's because it's being generated now
 144 13:35 <             Ursinha > (really)
 145 13:35 <             Ursinha > every 15 minutes
 146 13:35 <            rockstar > Ursinha, oh, I assumed it was because we were awesome.
 147 13:35 <             Ursinha > lol
 148 13:35 <             danilos > sinzui, right, and malone doesn't offer the option to search per-team, only per-application or per single person
 149 13:36 <             Ursinha > danilos: sinzui, bug 520569
 150 13:36 <              ubottu > Launchpad bug 520569 in malone "Add the ability of searching bugs from various assignees" [Low,Triaged] https://launchpad.net/bugs/520569
 151 13: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
 152 13:37 <             danilos > sinzui, right, but sometimes people from your team will land stuff in... launchpad-web project
 153 13:37 <             danilos > sinzui, and who'll ensure that QA happens there?
 154 13:37 <             Ursinha > sinzui: thanks for explaining your case
 155 13:37 <              sinzui > I search launchpad-project too
 156 13:37 <              sinzui > tags work for project
 157 13: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
 158 13:38 <             danilos > sinzui, nobody will mind if you always worry about launchpad-project :)
 159 13:38 <             danilos > I still think this is a useful list to have
 160 13:38 <             danilos > if that's what we are arguing
 161 13:38 <             Ursinha > :)
 162 13: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
 163 13:39 <              sinzui > I do not need a list.
 164 13:39 <             Ursinha > if that's what we are arguing :P
 165 13:40 <             Ursinha > sinzui: are you happy with the things you have today?
 166 13: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
 167 13: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?
 168 13:43 <             Ursinha > sinzui: if I add a list of launchpad-registry to that list, would help?
 169 13: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
 170 13:43 <             Ursinha > danilos: it's lp-qa-tools
 171 13:43 <              sinzui > s/I and a/I am a/
 172 13:43 <             Ursinha > sinzui: in general those items fall in the launchpad itself team, and me and matsubara take care of that
 173 13: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
 174 13:44 <             danilos > sinzui, at least IMHO, but it's a different topic, so let's not discuss it now :)
 175 13:44 <              sinzui > You have never QAed my contributions to blueprints, answers, or foundations
 176 13:44        [Nick] salgado-lunch is now known as salgado
 177 13:44        [Nick] gary_poster is now known as gary-lunch
 178 13:45 <             Ursinha > sinzui, danilos, I'll send the email to the list, and we can discuss the details in there, what about that?
 179 13:45 <             danilos > sinzui, that's because we've done a bad job with QA in general
 180 13:45 <              sinzui > And I do QA all contributors work who land something in blueprints, answers or registry.
 181 13: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")
 182 13:47 <             danilos > anywaay, let's move on
 183 13:48 <             Ursinha > ok
 184 13:48 <             Ursinha > thanks danilos and sinzui for speaking up
 185 13:48 <             Ursinha > :)
 186 13:48 <             Ursinha > list of untriaged bugs in launchpad-project, a picture of a moment before the meeting: http://paste.ubuntu.com/397314/
 187 13:48 <             danilos > thanks
 188 13:48 <             Ursinha > or
 189 13:48 <             Ursinha > <flood>
 190 13:49 <             Ursinha > Soyuz (soyuz): 79
 191 13:49 <             Ursinha > launchpadlib  (launchpadlib): 25
 192 13:49 <             Ursinha > OOPS Tools (oops-tools): 22
 193 13:49 <             Ursinha > Launchpad Developer Utilities (lp-dev-utils): 9
 194 13:49 <             Ursinha > Launchpad QA Utilities (lp-qa-tools): 7
 195 13:49 <             Ursinha > Launchpad Development Wiki Moin theme (launchpad-dev-moin-theme): 6
 196 13:49 <             Ursinha > Launchpad Bugs (malone): 5
 197 13:49 <             Ursinha > Launchpad Auto Build System (launchpad-buildd): 4
 198 13:49 <             Ursinha > Launchpad Help Wiki Moin theme (launchpad-help-moin-theme): 4
 199 13:49 <             Ursinha > launchpad-web (launchpad-web): 3
 200 13:49 <             Ursinha > Launchpad Translations (rosetta): 3
 201 13:49 <             Ursinha > Launchpad CSCVS (launchpad-cscvs): 2
 202 13:49 <             Ursinha > launchpad-loggerhead (launchpad-loggerhead): 2
 203 13:49 <             Ursinha > Launchpad News WordPress Theme (launchpad-news-wordpress-theme): 2
 204 13:49 <             Ursinha > Launchpad Buildbot Configuration (lpbuildbot): 2
 205 13:49 <             Ursinha > trac-launchpad-migrator (trac-launchpad-migrator): 2
 206 13:49 <             Ursinha > Launchpad Documentation (launchpad-documentation): 1
 207 13:49 <             Ursinha > </flood>
 208 13:49 <             danilos > bigjools, do you think soyuz will need any help in triaging?
 209 13:49 <            bigjools > if you think you can help, yes please
 210 13:50 <            bigjools > if it's obvious what to do, do it (but let me know)
 211 13:50 <             danilos > bigjools, I'll go 'invalidate' a dozen or so, just to give a hand
 212 13:50 <            bigjools > bug fixing for dummies
 213 13:50 <             Ursinha > danilos: I have a script that does that.... kidding
 214 13:50 <             Ursinha > :P
 215 13:50 <           matsubara > I'll take care of the 22 New items for oops-tools
 216 13:50 <             danilos > bigjools, and I'll mark a bunch of others as 'incomplete' with a comment "Why do you think it is so?"
 217 13:50 <           matsubara > [action] matsubara to triage open oops-tools bugs
 218 13:51 <            rockstar > Fail. launchpad-code isn't in that list.
 219 13:51 <             danilos > rockstar, this time it probably means you are amazing
 220 13:51 <           matsubara > that's because you have 0 new oopses
 221 13:51 <             Ursinha > rockstar: because it has no new bugs
 222 13:51 <           matsubara > rockstar, good job!
 223 13:51 <           matsubara > :-)
 224 13:51 <            rockstar > daniloff, yeah, I was fishing...
 225 13:51 <            rockstar > :)
 226 13:51 <           matsubara > s/oopses/bugs/
 227 13:51 <             Ursinha > you are all so funny today :)
 228 13:51 <             Ursinha > [action] matsubara to triage open oops-tools bugs
 229 13:51 <             MootBot > ACTION received:  matsubara to triage open oops-tools bugs
 230 13:52 <            rockstar > Ursinha, looks aren't everything though
 231 13:52 <             Ursinha > [action] Ursinha to triage open lp-qa-tools bugs
 232 13:52 <             MootBot > ACTION received:  Ursinha to triage open lp-qa-tools bugs
 233 13:53 <             Ursinha > rockstar: sorry? :)
 234 13:53 <            rockstar > Ursinha, <Ursinha> you are all so funny today :)
 235 13:54 <             Ursinha > anyway, matsubara and I want to reactivate a section in this meeting, QA stats of the week
 236 13:54 <             Ursinha > then we can discuss the status of bug triage and QA
 237 13:55 <             Ursinha > that's all from me, I'm done here
 238 13:55 <             Ursinha > anyone willing to add something?
 239 13:56 <             Ursinha > ok, so sorry for taking so long 
 240 13:56 <             Ursinha > Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
 241 13:56 <             Ursinha > #endmeeting
 242 13:56 <             MootBot > Meeting finished at 11:56.

DevelopmentMeeting20100318 (last edited 2010-03-18 21:40:27 by ursinha)