12:02:07 #startmeeting 12:02:07 Meeting started Tue Aug 18 12:02:07 2015 UTC. The chair is rafi. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:02:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:02:50 time for todays bug trige meeting 12:03:05 #info Agenda https://public.pad.fsfe.org/p/gluster-bug-triage 12:03:27 #topic roll call 12:03:56 let's see who all are with us 12:03:58 :) 12:06:03 let's wait for some time 12:09:12 * skoduri is here 12:09:44 * jiffin is here 12:09:53 * kkeithley_blr is late 12:10:05 meghanam is here 12:10:41 * ndevos looks around 12:11:25 #chair meghanam 12:11:25 Current chairs: meghanam rafi 12:12:28 moving to next topic 12:12:54 #topic status of last week's action items 12:13:34 #info Agenda https://public.pad.fsfe.org/p/gluster-bug-triage 12:14:22 #topic pranithk will send a reminder on how to find and fix bugs, attract new contributors 12:14:41 pranithk is on leave today 12:14:50 Can anyone else update on this? 12:15:18 I think Pranith can do that next week :) 12:15:24 ok 12:15:48 #action pranithk will send a reminder on how to find and fix bugs, attract new contributors 12:15:59 moving to next topic 12:16:24 #topic hagarth start/sync email on regular (nightly) automated tests 12:17:00 moving it to next week 12:17:15 #action hagarth start/sync email on regular (nightly) automated tests 12:17:29 #topic someone will send a reminder to the users- and devel- ML about (and how to) fixing Coverity defects 12:18:04 I don't remember seeing it on the list. 12:18:15 any one need to take this action item ? 12:19:32 I can take this one 12:19:37 I think that is basically for pranith>? 12:19:44 I can check with lalatenduM who had done that before 12:20:00 I am okay if it can be clubbed with 12:20:03 pranith's AI 12:20:04 Thanks Soumya 12:20:04 :) 12:20:12 combine the "find + fix bugs" with coverity :) 12:20:30 sounds good ;) 12:20:55 #action soumya to send send a reminder to the users- and devel- ML about (and how to find and fix ) Coverity defects 12:21:07 moving to next action item 12:21:27 #topic lalatenduM and ndevos need to think about and decide how to provide/use debug builds 12:21:36 ndevos: do you want to update ? 12:21:43 on this ? 12:21:50 we're still thinking about that... sometimes 12:23:01 once distaf is in place for testing ,we can do tests with debug builds 12:24:35 when we say "debug builds" what are we really saying? Compiled -g -O0 and installing the -debuginfo RPM during testing? (versus compiled -g -O2 and the -debuginfo RPM isn't installed during testing) 12:25:19 builds with "./configure --enable-debug" 12:25:52 and yes, using RPMs 12:26:01 which I think means compile with -g -O0, correct? 12:26:34 probably, I would need to check 12:27:24 kkeithley_blr: yes , i think so 12:28:23 rafi, meghanam: next topic? 12:28:42 #topic group triage 12:28:47 #info 19 new bugs that have not been triaged yet : http://goo.gl/WuDQun 12:29:15 We have an etherpad. Each of you can select a bug and write your name against it. 12:29:34 nice, got a link to the etherpad? 12:29:37 https://public.pad.fsfe.org/p/fSV06Zf7H0 12:29:51 The etherpad is empty though. 12:30:00 Can you help us put the bug numbers there? 12:30:12 hmm, wasnt there an etherpad in a previous meeting? 12:30:18 it had the command to create the contents 12:30:53 this one: https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:31:23 but I did not add those bugs listed there, they are less than 19, so I dont know if that is current? 12:32:58 I have updated the etherpad https://public.pad.fsfe.org/p/fSV06Zf7H0 12:33:06 with the bugs from the query 12:33:17 Thanks skoduri 12:33:38 let's start triaging :) 12:33:51 rafi: which etherpad?? 12:33:56 * hchiramm_ locks 1252374 12:34:00 * ndevos corrected https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:34:22 hchiramm_: we use etherpad locking now :) 12:34:24 okay so which one are we using ? :) 12:34:39 ndevos, :) 12:34:39 lets use https://public.pad.fsfe.org/p/gluster-bugs-to-triage ? 12:34:47 skoduri: yes 12:34:48 yes 12:34:50 okay 12:34:51 * ndevos waits for rafi and meghanam to make a call 12:35:09 meghanam, you need to strike that line as well 12:35:19 hchiramm_: pls use this etherpad and add your name to the line 12:35:28 skoduri: Yes. Once I am done triaging. 12:35:31 hchiramm_: and strike off once you finished 12:36:22 rafi, hchiramm_: not when finished, strike through when going to triage? 12:36:36 rafi, yeah, strike when u take that 12:36:41 ok 12:38:19 kkeithley_blr: you know we use the etherpad-locking now, RIGHT!? 12:38:48 ndevos: yes, that's what I think I'm doing 12:39:11 s/think/believe/ 12:39:22 kkeithley_blr: hmm, I dont see your name in any of the bugs, and the one I just wanted to triage was already done by you... 12:39:51 1251821 has my name and strike-through on my screen 12:40:00 kkeithley_blr, https://public.pad.fsfe.org/p/gluster-bugs-to-triage 12:40:08 that's the one we're using now. 12:41:28 sigh 12:48:56 rafi, meghanam: all triaged? 12:49:08 Not yet. 12:50:25 * ndevos patiently waits 12:50:47 ndevos: do you want to look into https://bugzilla.redhat.com/show_bug.cgi?id=1252302 ? 12:51:31 ndevos: I'm not familiar with BD-xlators 12:51:50 rafi: what makes you think I am? 12:52:07 ndevos: you are ndevos :) 12:52:17 *because 12:52:35 * ndevos feels recursive 12:52:56 ndevos, kkeithley any idea who maintains BD xlator? 12:53:13 ohh sorry haven't checked history 12:53:15 mohan from IBM, I think... well, 'maintains' 12:53:30 do you know the mail-id? 12:54:11 got it - mohan@in.ibm.com 12:54:40 I think all the details in that bug are clear enough 12:54:50 right 12:54:56 it even mentions to not use readdirp and the problem does not occur 12:55:04 ndevos: skoduri : let us know when you guys finishes with 1250786 and 250786 ? 12:55:36 * ndevos is done with the bugs, he put one on NEEDINFO 12:56:00 ndevos: ok 12:56:25 done with group triage 12:56:31 Moving forward 12:56:32 * ndevos \o/ 12:56:41 #topic open floor 12:57:00 Is there anything you want to discuss? 12:57:46 make sure to include the etherpad for the triage/locking next time :) 12:58:05 and prepare it, install the python-bugzilla package on your machines 12:58:42 Sure Niels. Sorry for the inconvenience. We started a little late today. 12:58:58 no problem :) 12:59:01 it is hard to know whether some one finished triging a bug or not 12:59:17 oh, yes, not sure how we can improve that 12:59:18 it is difficult to keep refreshing the bug list 12:59:42 that's why i was telling to strike only if we finish it 13:00:03 add name when we lock it, and strike when we finish 13:00:07 what do you think ? 13:00:08 I guess we could do that, and prepend the bug-lines with your name 13:00:09 ndevos: hchiramm_ 13:00:23 That sounds better actually 13:00:31 #agreed 13:00:33 just update the instructions in the etherpad, so that we can try it next week 13:01:00 rafi, too much process to triage a bug :) 13:01:03 #agreed to prepend the name when we take a bug to triage and strike when we finish 13:01:10 and a reminder to look into those changed instructions :) 13:01:18 hchiramm_: propose a new idea :) 13:01:53 sure.. here it is 13:02:28 #action on rafi to update the etherpad on new instructions for bug triaging 13:02:34 ndevos 13:02:40 123 13:02:42 234 13:02:49 rafi 13:02:50 567 13:02:51 456 13:02:54 678 13:03:12 just put the name of attendees and divide the list 13:03:14 :) 13:03:38 well, some bugs will take more time to triage than others? 13:04:00 and, not everyone feels comfortable to triage all components 13:04:25 And not everybody will be there for the entire meeting right? 13:04:33 thats possible too 13:04:41 we also have regular late joiners 13:04:54 * rafi believes ndevos and hchiramm_ are exceptional 13:04:57 ... and people pushing me to leave 13:05:35 * meghanam wonders why 13:06:03 * ndevos points to the clock 13:06:56 Are there any other opinions? 13:07:04 NO! :D 13:07:58 Alright then. We'll put the new instructions on the etherpad and see you tomorrow for the community meeting! 13:08:11 #endmeeting