12:00:01 #startmeeting Gluster Bug Triage 12:00:01 Meeting started Tue Dec 8 12:00:01 2015 UTC. The chair is Manikandan. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:01 The meeting name has been set to 'gluster_bug_triage' 12:00:07 #info agenda: https://public.pad.fsfe.org/p/gluster-bug-triage 12:00:13 #topic Roll Call 12:00:32 * rafi1 is partially here 12:00:44 * skoduri is here 12:01:10 * Manikandan expects more participants as we have around 25 bugs to triage 12:01:42 jiffin, hgowtham, ashiq, ^^ 12:01:43 * atinm is here 12:01:57 but partially though :( 12:02:00 * hgowtham is here 12:02:06 * jiffin ihere 12:02:10 atinm, np :) 12:02:33 Should we wait for some more participants? 12:02:56 5 should be good enough to start? 12:03:05 atinm, okay!! 12:03:16 Going on to last week action items 12:03:22 people will join eventually 12:03:27 #topic skoduri and ndevos will document how people can get bug notifications for specific components 12:03:32 skoduri, any updates on this? 12:04:05 Manikandan: we can move to the end 12:04:23 skoduri: is not here 12:04:28 jiffin, sure 12:04:30 right now 12:04:45 #topic atinm will try to get a followup from Naga on http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12760/focus=12801 12:05:11 Manikandan, its a pretty old action item and I do believe Naga has already replied to this thread 12:05:21 * atinm is searching for the link 12:05:44 Manikandan, sorry had to step out for few min 12:05:57 skoduri, np 12:06:04 we haven't done that..please keep it for next week 12:06:08 Manikandan, here is the link : http://www.gluster.org/pipermail/gluster-devel/2015-November/047078.html 12:06:42 #action skoduri and ndevos will document how people can get bug notifications for specific components 12:06:59 atinm, thank you :-) 12:07:28 Since none of the other assignees are there, moving to group triage 12:07:43 #topic Group Triage 12:07:51 #link https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:07:58 The bug triage process is documented here 12:08:05 #link http://gluster.readthedocs.org/en/latest/Contributors-Guide/Bug-Triage/ 12:08:13 Please enter your name in the beginning of the bug you are going to triage 12:08:20 Strike the bug out from the list once triaging is done 12:12:34 * Humble is here 12:21:01 On what basis we have picked up old bugs? 12:21:28 was there any selection criteria? 12:21:52 atinm, there is a longer list of older BZ's that need to be triaged, we just run the query and take the top 10 bugs out of it 12:22:16 Manikandan, 10 oldest bugs right? 12:22:53 Manikandan, I am not sure if it's oldest, I just run this query 12:23:01 'https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&product=GlusterFS&f1=keywords&o1=notsubstring&v1=Triaged 12:23:22 and took the top ten from the list 12:24:55 Manikandan, ideally we should sorted on the bug id to pick the oldest ones, what do you think? 12:25:03 s/should/should have 12:25:16 atinm: there were around 103 backlog bugs, so we planned to triage them out 12:25:22 atinm: +1 12:25:25 atinm, that makes more sense to take the oldest 12:26:00 From next triage, we will follow up 12:29:49 Manikandan, may be we can have a filter based on the date/period 12:30:01 that would help us to sort it out. 12:30:14 Humble, hmm sure 12:31:01 Manikandan, r we done ? 12:31:14 Humble, few more bugs 12:32:14 Humble, could you look into BZ-1058300 12:32:30 Manikandan, let me check :) 12:32:39 Humble, thanks :) 12:33:02 Manikandan, skoduri is already on it 12:33:18 Humble, cool 12:33:27 skoduri++ :) 12:36:13 done 12:36:29 skoduri, thanks :) 12:37:03 We are finally done with group triage :P 12:37:07 there are only a couple BZs that are older than the old ones we did today. 764795, 860466, 1004546, and 1010068 12:37:20 #topic Open Floor 12:37:22 maybe make sure we get those on the list for next week 12:37:30 kkeithley_, thanks for the update 12:37:50 Sure will add it to the list 12:38:00 what do we do to the older bugs which may not be applicable/exist in the latest release? 12:38:13 I have put need_info on reporter to re-test and update 12:38:36 what is no one actively responds? How long shall we keep such bugs? 12:39:06 */is/if 12:39:33 Aren't we already closing such bugs after a period of time and asking them to reopen if they could find in latest build? 12:39:42 send them a reminder? 12:40:11 If I were you, I would have taken a call based on the release version, if its 3.5 then I wouldn't really mind to close it saying Won't fix since its going to be EOLed pretty soon once 3.8 arrives? 12:40:32 3.8 is still a couple months away. 12:40:55 atinm, but if that seem to be a valid issue which may happen even on latest releases? 12:41:09 and if the bug still exists in newer release(s) we should change the version 12:41:16 kkeithley_, agree 12:41:45 skoduri, lets move on? 12:42:00 I do not remember correctly, how long can we keep bugs with need_info before closing it 12:42:54 skoduri, 3-4 weeks is a good enough time, this was discussed few months ago in one of the meeting 12:43:42 atinm, thanks..I keep forgetting ..so wanted to confirm once :) 12:44:41 Rafi has alrady set up a doodle poll regarding the suitable timing for bug triage meeting 12:45:09 * jiffin casted my votes 12:45:09 yep.. 12:45:17 me too :) 12:45:19 * Manikandan too 12:45:22 did he sent a mail to gluster users ? 12:45:31 sent/send 12:45:43 YEs 12:45:46 Yeah he sent to gluster-users as well 12:45:57 oh..ok 12:46:24 kkeithley_, atinm Humble skoduri jiffin hgowtham rafi1, anything else to discuss? 12:46:41 Manikandan, nothing from my side 12:46:42 no from me 12:46:48 none from me as well 12:46:49 Manikandan, no 12:46:49 No. I just triaged three of those four older bugs, so.... 12:47:01 kkeithley++ 12:47:02 Humble: kkeithley's karma is now 3 12:47:05 kkeithley_++ :D 12:47:06 kkeithley_, thanks again ;-) 12:47:37 Anyone interested to host next week's bug triage meeting? 12:47:39 before we finish, do we really monitor the bugs which are triaged ? :) 12:47:45 ndevos has mentioned in one of previous, if the status of BUG is corrected properly please inform the assignee 12:47:48 kkeithley_++ 12:47:49 hgowtham: kkeithley_'s karma is now 6 12:48:32 hopefully maintainers are watching Bugzilla and looking at the bugs that are assigned to them. Is that not the case? 12:48:38 s/corrected/inot corrected/ 12:48:55 its expected to work that way, but I am not sure.. 12:48:58 That's how I track incoming traffic for glusterd :) 12:49:28 we can put a needinfo on assigne? 12:49:29 atinm++ thanks 12:49:50 if he is already posted the patch 12:50:03 I do feel that its everyone's responsibility, not only for maintainers 12:50:07 ask him to change the status accordingly 12:50:09 jiffin, just to remind them about the incorrect status? 12:50:11 kkeithley_, hopefully every maintainer is doing that. but I am not sure 12:50:19 Yes 12:50:30 jiffin, hmm (y) 12:50:37 Yes, it's everyone's responsibility. 12:50:41 atinm: yes it is , but not followed properly 12:51:02 atinm, true.. for that there should be proper filtering at everyones end to sort the bugs at their component 12:51:25 but I dont know whether people really know about the bug mailing list itself 12:51:28 so the question 12:51:51 Humble, yes that's the trick 12:52:14 Humble, for me I have a filter applied in my mail box, and that too for new bugs and existing bugs 12:52:35 documenting it should be helpful, I believe ndevos & skoduri are already into it 12:52:42 atinm, yup 12:53:00 And management needs to remember that there is more to Gluster than just downstream. I think they know that. But sometimes we get stuck in a "downstream only" mindset. 12:53:16 atinm, yes..hopefully by next bug triage meeting will send out the query which one can use to filter 12:53:17 afair, we sent a mail about the process. 12:53:49 atinm, do u think we can really increase the participation in the bug traiging meeting by asking the scrum team to join ? 12:54:01 I see nfs ganesha is active here :) 12:54:10 indeed 12:54:13 kkeithley++ skoduri++ jiffin+ 12:54:27 ndevos would be here too, but he is on PTO this week 12:54:31 like that if every scrum master can pull their team, this meeting will be really effective 12:54:31 ndevos++ 12:54:32 I tried, but failed multiple times 12:54:32 kkeithley_: ndevos's karma is now 2 12:54:41 yeah, ndevos++ jiffin++ 12:55:19 * Manikandan feels quota team is very small :P 12:55:20 we need to discuss this. lets see.. 12:55:38 Manikandan, but still u can mark the presence :) 12:55:47 Humble, sure, I will :-) 12:55:54 I mean ur team :) 12:56:01 yes, if every scrum master was here, they could triage their own bugs, and then they'd be right on top of their own bugs 12:56:11 kkeithley_, +1 12:56:14 atinm++ 12:56:16 Humble: atinm's karma is now 1 12:56:19 kkeithley_, indeed.. 12:56:24 and people don't have to wait for the Bug Triage meeting to triage their own bugs 12:56:38 s/people/scrum masters/ 12:56:55 atleast it matters a lot for the stability of the product and to catch the bug at the earliest. 12:56:57 yep . 12:57:09 yes that should be the practice 12:57:48 Anything else atinm Humble kkeithley_ ? 12:57:53 I think I should write a blog about how do our team triage bugs 12:58:06 atinm: +1 12:58:12 atinm++ , please 12:58:19 so that others can also practice. 12:58:25 sure 12:58:28 also try once again to pull ur team here :) 12:58:32 Will do that in some time 12:58:46 Manikandan, once again nothing from me.. :) 12:59:05 * atinm echoes the same 12:59:10 Anyone interested in hosting next week's bug triage? 12:59:26 * Manikandan echoes the same old question :P 12:59:44 * Humble : I am busy next week with meetings :) 13:00:04 atinm, and jiffin is also busy with meeitngs 13:00:07 btw next week Amye is here in Bangalore. 13:00:22 hgowtham, ? :) 13:00:24 won't she be busy with the planning meetings? 13:00:45 kkeithley_, yes, we also have some community meetings next week 13:00:48 Along with Ric, and jdarcy 13:00:52 Humble, yea sure i'll try 13:00:57 also announced a meetup. 13:00:59 kkeithley_, true 13:01:10 thanks hgowtham++ , take help from Manikandan if needed 13:01:10 Humble, I saw, dec 18? 13:01:15 Manikandan, yes 13:01:25 yea i'll talk to Manikandan about it :) 13:01:35 hgowtham, thanks :-) 13:01:43 Manikandan, yw 13:01:45 :) 13:02:02 thanks Manikandan++ 13:02:10 hchiramm++ hgowtham++ atinm++ jiffin++ skoduri++ kkeithley_++ rafi1++, thank you all :-) 13:02:33 Manikandan++ 13:02:34 rafi1: Manikandan's karma is now 1 13:02:51 bye 13:02:57 cya 13:03:25 Manikandan, do endmeeting 13:03:36 #endmeeting