12:01:08 #startmeeting 12:01:08 Meeting started Tue Nov 4 12:01:08 2014 UTC. The chair is ndevos. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:22 hello all, welcome to todays Bug Triage meeting 12:01:28 #agenda https://public.pad.fsfe.org/p/gluster-bug-triage 12:01:34 #topic Roll Call 12:01:47 so, who's here today? 12:02:11 * kkeithley1 is here 12:02:47 lalatenduM, Humble, overclk, ... anyone else? 12:02:56 #chair kkeithley_ 12:02:56 Current chairs: kkeithley_ ndevos 12:04:05 hmm, if it's only kkeithley_ and me, I doubt we should do the triage today... 12:04:47 * Humble here 12:04:50 well, daylight savings ? 12:05:02 kkeithley_: only you and jdarcy :) 12:05:07 messed me up yesterday 12:05:18 * krishnan_p is here 12:05:32 #chair Humble krishnan_p 12:05:32 Current chairs: Humble kkeithley_ krishnan_p ndevos 12:05:55 I guess we wont cancel todays meeting then 12:06:15 #topic Status of last weeks action items 12:06:27 * lalatenduM is here and is late to the meeting 12:06:39 seems that either the person is not there, or the item is marked as [done] 12:06:43 #chair lalatenduM 12:06:43 Current chairs: Humble kkeithley_ krishnan_p lalatenduM ndevos 12:07:03 so, we'll jus jump to the next topic: 12:07:08 #topic Group Triage 12:07:31 nobody proposed any particular bugs 12:07:45 if you got some, it is now the time to mention it 12:08:12 we also have no bugs with NEEDINFO(bugs@gluster.org) 12:08:42 #topic Bugs filed since last week 12:09:00 http://goo.gl/0IqF2q contains the list that needs checking 12:09:25 looks like people have been busy, 23 new bugs in one week! 12:09:49 please triage some, I'll take the disperse ones :D 12:10:17 * kkeithley_ is looking 12:11:07 ndevos, how are we spliiting the bugs to be looked at? 12:12:00 krishnan_p: we use irc-locking 12:12:19 krishnan_p: pick a bug, and mention here that you'll triage it 12:12:38 1158088 12:12:43 ndevos, OK :) 12:12:54 1158622 + all disperse 12:13:43 1158654 12:15:28 1158123, 1158130 have been opened by Philip Spencer and both have patches attached by him. What do you guys suggest? Shall we submit the patches to gerrit on his behalf or suggest to him to submit it via gerrit? 12:16:28 I'd submit on his behalf. 12:16:34 submit on his behalf and cc him 12:17:01 krishnan_p: I tend to ask if the reporter wants to post the patch, or if they prefer me to post them 12:17:21 krishnan_p: mark the bug Triaged, and add the Patch keyword 12:17:51 we have quite some bugs marked with Patch, we need someone to check those and post them 12:18:17 ndevos, done. 12:19:16 1158067 12:19:58 This bug has a needinfo on the reporter. I have requested for logs from the reporter when the issue was seen. He has not come back. Does this bug qualify for the Triaged keyword? 12:21:36 1159269, 1159284 12:21:42 krishnan_p: I do not think Triaged is appropriate in that case 12:22:10 ndevos, OK. 12:22:19 https://bugzilla.redhat.com/show_bug.cgi?id=1158126 has a patch attached to it 12:22:25 sorry to disturb... bug 1159485 seems a duplicate of 1149727, but I can't change it... 12:22:50 * krishnan_p is building his intuition for the triage process... 12:23:29 krishnan_p, ndevos are you guys marking bugs by Philip Spencer (with patch) as triaged ? 12:24:17 lalatenduM, I just did so for two of the bugs he had reported 12:24:41 I have in fact, irc-locked it as per ndevos' recommendation :) 12:24:53 who did hagarth say was going to be 3.6 release wrangler? 12:25:44 kkeithley_, not decided I think 12:26:06 oh, I thought there was a volunteer. Will find out tomorrow 12:26:17 in the meeting 12:26:19 raghavendra bhat volunteered to be 3.6 release maintainer IIRC. 12:26:29 kkeithley_, yeah there was a volunteer 12:26:48 kkeithley_, but not sure if it was confirmed 12:27:05 1159253, I'm going to assign to him. We can change it if that turns out not to be the case 12:27:08 I have not seen a confirmation, nor a rejection 12:27:24 kkeithley_, here goes - http://supercolony.gluster.org/pipermail/gluster-devel/2014-October/042661.html 12:28:02 1159221 <- mine! 12:29:29 ndevos, looks like you have already looked in to 1158622 12:30:02 lalatenduM: yes, indeed 12:30:10 * lalatenduM forgot that ndevos is in NFS team now :) 12:30:23 I'll take 1158129 too 12:30:36 1158622 12:30:48 everyone wants that one 12:30:49 philip spencer is on a roll. He has four bugs opened, all of them with a patch attached. 12:30:57 krishnan_p: awesome! :D 12:31:05 philipspencer++ 12:31:13 philipspencer++ 12:31:16 krishnan_p, yeah :) 12:31:20 oh, I got one too from him now 12:31:33 I think we should nudge him to have these patches appear on gerrit 12:31:35 ndevos, sadly, I am not able to verify if his patches are correct :( 12:31:43 hagarth, yup 12:31:56 as long as they're not "segv here, check for nullp and branch around it" patches 12:31:59 anyone have taken a look at https://bugzilla.redhat.com/show_bug.cgi?id=1159172 12:32:09 it looks like a bug on mainline 12:32:23 a feature request 12:33:23 ndevos, ^^ should I move it to mainline 12:33:53 lalatenduM: yes, it is a feature request on mainline 12:33:57 lalatenduM: you can, yes 12:34:02 done 12:35:10 1158051 12:35:43 xavih: marked as duplicate, thanks! 12:35:43 ^^ I know Raghavendra Bhat works on USS and he is the reporter. Could we mark this Triaged? 12:36:01 another from philipspencer 1158120 , with patch :) 12:36:09 krishnan_p: probably, or if a patch has been posted, just change the status 12:36:12 krishnan_p: +1 to 1158051 12:36:38 krishnan_p: you can also assign the bug to him, if you think that is suitable 12:36:48 hagarth, ndevos, makes sense. OK 12:36:49 hagarth, we should get philipspencer to mailing lists and gerrit :) 12:36:59 lalatenduM, +1 12:37:20 does anyone know this guy? 12:37:57 krishnan_p, lalatenduM: did you ask Philip to post his patch to Gerrit already? can I copy/paste that comment? 12:38:08 lalatenduM: yeah 12:38:23 ndevos, nope 12:38:46 ndevos, I havent posted the comment (yet). I could do that though 12:38:55 1158226 12:39:15 ndevos, krishnan_p we can use http://www.gluster.org/community/documentation/index.php/Developers in our comment 12:39:24 ^^ this one has the patch committed. I am changing state to MODIFIED. SHould I also add the Triaged/Patch keyword? 12:39:43 krishnan_p: you do not have to, change the status is sufficient 12:39:50 hagarth, nice :), is he from community or rh? 12:40:01 krishnan_p, yes 12:40:02 ndevos, thanks. 12:40:18 lalatenduM: he is from uwaterloo.ca I think 12:40:26 ndevos, I think if we put triaged , it will not come up in bugzilla quesry 12:40:31 query* 12:40:55 hagarth, cool 12:41:20 ndevos, I will be adding a comment inviting Philip to gerrit in these two bugs - 1158120, 1158129 12:41:32 3.6.1 is not there in target milestone ? 12:41:35 utoronto.ca is Univ. of Toronto. 12:41:57 kkeithley_: right 12:42:11 I wonder if pspencer@fields.utoronto.ca is related to henry@zoo.toronto.edu 12:42:19 There's a couple Target Milestones we need added. Versions too 12:42:57 what are those 12:43:02 I can get it sorted .. 12:44:27 * krishnan_p thinks that it would suffice if we let Philip know of our process via one BZ comment and not as many as he as opened. 12:45:12 btw whats our approach if the patch comes through github ? 12:45:15 Humble: 3.6.1 and 3.6.2 target milestones would be nice to have 12:45:20 k 12:45:37 Humble: we normally encourage such submitters to appear on gerrit 12:45:58 hagarth, ok .. 12:46:00 thanks 12:46:38 ndevos, krishnan_p here is the comment I am putting 12:46:39 Philip, 12:46:39 Thanks for the patch. GlusterFS community uses gerrit to review patches. Please refer below link to know developer work flow in GlusterFS community. If you are interested to post the patch yourself , you are welcome to do so. If you want us to post the patch on your behalf let us know. 12:46:39 [1] http://www.gluster.org/community/documentation/index.php/Development_Work_Flow 12:47:28 LGTM 12:47:37 lalatenduM, I have already posted a comment and didn't give him the option where we post patches on his behalf. 12:48:05 krishnan_p, cool, I just wanted to be more friendly :) 12:48:55 +1, looks good 12:48:57 if they keep repeating we can notify them . for first patch its ok I think :) 12:49:01 lalatenduM, I think I was fairly friendly. See https://bugzilla.redhat.com/show_bug.cgi?id=1158120 12:49:01 lalatenduM, krishnan_p: lets see is we all can convince him, I just posted https://bugzilla.redhat.com/show_bug.cgi?id=1158129#c1 12:49:25 krishnan_p, yeah it is fine too 12:49:30 :) 12:49:44 ndevos, need an entry in wiki page for this :) 12:49:55 lol :) 12:50:15 Humble, I think so to. The message is very welcoming. 12:50:39 * Humble gss++ :) 12:50:44 I think http://www.gluster.org/community/documentation/index.php/Development_Work_Flow looks scary for 1st time visitors ;) 12:50:45 ndevos, good on 12:50:48 one* 12:51:08 what abt http://www.gluster.org/community/documentation/index.php/Simplified_dev_workflow 12:51:14 why ? 12:51:16 :) 12:51:48 Looks like all the bugs in the list are triaged. 12:51:52 then everyone will be skipping development workflow 12:51:56 lalatenduM: yes, I like that one more 12:52:15 krishnan_p: 1158120 is not marked Triaged? 12:52:46 ndevos, Yes. I overlooked it. 12:52:51 krishnan_p: ah, ok 12:53:12 #topic Bugs per version, needs cleanup of old bugs 12:53:17 #link http://goo.gl/IA7zaq 12:53:55 we've got rid of all the ON_DEV bugs, thats a + 12:54:18 but, there are still quite some bugs in older versions that we do not update anymore 12:54:39 we should move those bugs to newer versions, or close them if they have been fixed 12:55:02 I'd like to ask all of you, to have a look at a few of those bugs during the week 12:55:27 each bug that we can 'correct', is helpful for the community 12:55:33 ndevos: +1 to reduce overall backlog 12:55:38 Do we still need to look at 3.2 bugs ? 12:55:51 ndevos, would it help we picked a set of versions that we all could work on? 12:55:52 we'll look at them, but we won't fix them 12:56:29 krishnan_p: well, anything before 3.4 is legacy and should be checked/moved/closed 12:56:49 ndevos, OK. that answers my questions quite comprehensively. 12:56:56 the code path may be totatlly differeent in latest versions 12:57:27 so I am not sure what we do even if we see as a bug in 3.2 12:57:39 with our "support" schedule, we do a [ $CURRENT_VERSION - 0.2 ] maintenance 12:57:54 so, 3.4, 3.5 and 3.6 are in maintenance now 12:58:32 Humble: I guess we should try to figure out if that bug in 3.2 also affects the current version(s) 12:59:03 how much work should we do to confirm that a bug reported in, e.g. 3.1, is still a problem in a version we're maintaining? 12:59:15 yep.. good question 12:59:16 kkeithley_, +1 12:59:23 I feel its a waste of time 12:59:31 exactly 12:59:46 I think it depends on the maintainer of the component, get them involved if you have questions about it 13:00:29 for NFS, I'd like to know if there is a potential bug, and I would like to see it fixed in a current version 13:00:29 although I can't CLOSE/WONTFIX or even just CLOSE 859248 13:00:45 * lalatenduM thinks it might be a overkill for component owners 13:00:53 indeed 13:01:31 3.6 is out , so soon 3.4 should be moving maintenance phase.. 3.2 is -2 from maintenance version .. 13:01:53 lalatenduM: really depends on the bug 13:02:25 kkeithley_: what prevents you from doing that? 13:03:08 no pulldown menu on the state. Bug maybe my mouse has gone wonky. Seems to work in other windows though 13:03:25 kkeithley_: hmm, I can change it... 13:03:42 /me needs to leave now. See you tomorrow all tomorrow. I will catch what I missed from the MoM. 13:03:45 okay, probably something wack with my mouse atm 13:03:56 thanks krishnan_p, cya! 13:04:16 * Humble : on other way ,we can close those 3.2 bugs saying fixed in current version , in case its not fixed report back. :) 13:04:31 kkeithley_: I marked it CLOSED/INSUFFIECIENT_DATA 13:04:40 it was waiting on the reporter for a while 13:04:57 #topic open floor 13:05:11 anyone with a quick topic? 13:05:37 Humble: do you want to request those extra Version and Target Release versions? 13:05:42 Or shall I? 13:05:43 yep 13:05:55 kkeithley_, I have open request with bugzilla team 13:06:04 if u want I can follow up on the same request 13:06:10 whatever u prefer 13:06:36 One is enough. Unless they're not responding. Scott Haines can add them too, and he's pretty responsive 13:07:10 ok,, I wil follow up 13:07:23 3.6.1 and 3.6.2 target milestones 13:07:26 anything else ? 13:07:38 3.5.4? 13:07:56 #action Humble will request additional versions in Bugzilla 13:08:01 #action Humble - 3.6.{1,2}, 3.5.4 in TM .. 13:08:03 yes, 3.5.4 would be gppd 13:08:06 *good 13:08:07 3.4.7? 13:08:17 ok.. will add 3 13:08:33 Any other topics? 13:08:41 not from me 13:08:55 #endmeeting