15:03:34 <dmcbride> #startmeeting OPNFV Release
15:03:34 <collabot> Meeting started Tue Oct 11 15:03:34 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:34 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:03:34 <collabot> The meeting name has been set to 'opnfv_release'
15:03:43 <dmcbride> #topic roll call
15:03:51 <mtahhan__> #info Maryam Tahhan (SFQM)
15:03:53 <bryan_att> #info Bryan Sullivan
15:03:55 <leifmadsen> #info Leif Madsen
15:04:08 <mtahhan__> available on IRC only today
15:04:15 <dmcbride> #info David McBride
15:04:16 <kubi001> #info kubi
15:04:16 <fzhadaev> #info Fedor Zhadaev
15:04:26 <StuartMackie> #info Stuart Mackie
15:05:10 <ulik> #info Uli Kleber
15:06:01 <jose_lausuch> #info Jose Lausuch
15:07:02 <hujie> #info hujie
15:16:24 <Yifei1> #info Yifei Xue
15:30:37 <dmcbride> #topic Danube
15:30:47 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Projects+Intending+to+Participate+in+the+Danube+Release
15:31:07 <dmcbride> #info scenario status page ^^
15:31:56 * ChrisPriceAB needs to drop off, will check the logs later (scribe well)
15:44:19 <leifmadsen> more ideal is that folks are continually triaging by reviewing their dashboards daily
15:44:29 <leifmadsen> that saves a lot of the 1-2+ hour meetings
15:44:51 <leifmadsen> when you do it consistently, you don't spend much time on it
15:45:37 <leifmadsen> especially if you need to assign back to the reporter -- if you do it 2-3 weeks later, you're unlikely to get feedback from the reporter, as they've likely moved on, and will have no interest (or ability) to reproduce issues and provide the info
15:45:39 <jmorgan1> i think dmcbride comments are general guidelines for how to do a triage
15:46:07 <jmorgan1> i'm sure projects can adjust as makes sense including # of meetings, legnth of meetings, etc
15:46:07 <leifmadsen> Understood, I'm just adding additional information based on what I've learned as a bug marshal for several projects
15:46:23 <jmorgan1> sure, makes sense
17:35:21 <dmcbride> leifmadsen: jmorgan1 One of the benefits of the triage meeting is that you have multiple people reviewing issues and making decisions together
17:35:49 <leifmadsen> oh I understand what the purpose of the triage meeting is for :)
17:36:06 <leifmadsen> typically though, that's not always (in my experience... usually) for the triage process. That's more for sprint planning.
17:36:06 <dmcbride> leifmadsen: jmorgan1 This helps to avoid errors that an individual might make
17:36:23 <leifmadsen> Ideally the general triage process will have already happened to vet out issues that don't have enough info, etc
17:36:36 <leifmadsen> you don't decide if you'll actually work on something in the triage meeting
17:37:27 <leifmadsen> and triage should be more about whether the issue was filled out correctly, has enough applicable data, is a generally useful issue etc.  Beyond that, the rest of the "is this a thing we care about" would happen during a scrum (or other type of planning) meeting
17:37:38 <dmcbride> I guess I should end the meeting :)
17:37:42 <dmcbride> #endmeeting