12:01:35 #startmeeting Gluster Community Weekly 12:01:35 Meeting started Wed Dec 2 12:01:35 2015 UTC. The chair is hagarth. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:35 The meeting name has been set to 'gluster_community_weekly' 12:01:53 agenda - https://public.pad.fsfe.org/p/gluster-community-meetings 12:02:06 #topic Roll Call 12:02:09 * Humble is here.. 12:02:15 * jiffin is here 12:02:21 who do we have here today? 12:02:22 o/ 12:02:22 * JustinClift1 2 12:02:24 * jdarcy is. 12:02:32 * msvbhat is here 12:02:37 * anoopcs is here 12:02:42 * ndevos is there 12:02:46 * raghu is here 12:03:04 let us get going 12:03:18 #topic AIs from last week 12:03:23 AI - ndevos send out a reminder to the maintainers about more actively enforcing backports of bugfixes 12:03:37 aaah! I knew I missed something 12:03:39 * Manikandan is here 12:03:42 * poornimag is here 12:03:51 ndevos: ok, let us track it for next week 12:04:03 yes please 12:04:07 #action ndevos to send out a reminder to the maintainers about more actively enforcing backports of bugfixes 12:04:24 next AI - raghu to call for volunteers and help from maintainers for doing backports listed by rwareing to 3.6.8 12:04:30 * hgowtham is here 12:04:54 * rjoseph is little late 12:05:02 raghu: any updates here? 12:05:17 ahh I missed it. Will do it by next week. 12:05:23 raghu: ok 12:05:30 * atinm arrives late 12:05:31 #action raghu to call for volunteers and help from maintainers for doing backports listed by rwareing to 3.6.8 12:06:02 next AI - rafi1 to setup a doodle poll for bug triage meeting 12:06:25 we don't have rafi today, is this still needed? 12:06:25 That was discussed in yesterday's bug triage meeting. 12:06:39 jiffin: ok and what was the outcome? 12:06:47 The timings for poll is decided 12:07:10 I hope rafi will setup the doodle pretty soon 12:07:16 jiffin: ok cool 12:07:28 tracking this till the poll goes out 12:07:35 #action rafi1 to setup a doodle poll for bug triage meeting 12:07:47 next AI - rastar and msvbhat to publish a test exit criterion for major/minor releases on gluster.org 12:07:52 msvbhat: any update on this one? 12:08:24 NO, rtalur sent a mail. I can send a patch to gluster.org 12:08:35 I mean, if the suggestions are final 12:08:48 I can incorporate that, and send a pull request 12:09:14 msvbhat: maybe we can start with what we have and incrementally update that based on feedback? 12:09:35 hagarth: Yeah, That works too. 12:10:10 msvbhat: ok, thanks 12:10:17 hagarth: I will send a pull request then 12:10:27 msvbhat: would that be in the glusterdocs repo, or in glusterfs-specs? 12:10:28 #action rastar and msvbhat to publish a test exit criterion for major/minor releases on gluster.org 12:10:40 ndevos: I would expect this to be in glusterweb 12:10:48 ndevos: I think glusterweb? 12:10:50 Okay 12:10:57 oh, ok 12:11:36 ok, moving on 12:11:50 next AI - kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla,  github 12:12:05 kshlm, csim: any updates here? 12:12:40 I guess they are not around, carrying this AI for next week 12:12:46 #action kshlm & csim to set up faux/pseudo user email for gerrit, bugzilla,  github 12:13:08 next AI - Need to decide if fixing BSD testing for release-3.6 is worth it 12:13:28 me and rastar did have some actions here, could not get it done last week. so this moves ahead for next week. 12:13:33 #action Need to decide if fixing BSD testing for release-3.6 is worth it. 12:13:47 next AI - amye to get on top of disucssion on long-term releases. 12:14:11 I pinged her about this, it's currently queued behind other things. 12:14:43 jdarcy: ok, should we drop/retain this from the AI list? 12:15:01 Let's retain this. 12:15:06 ok 12:15:20 #action amye to get on top of disucssion on long-term releases 12:15:30 next AI - hagarth_ to     start a thread on review backlog 12:15:39 I will be doing it this week 12:15:41 so.. 12:15:45 #action hagarth_ to     start a thread on review backlog 12:16:11 moving on 12:16:14 we are so bad in doing our assigned action items :-/ 12:16:40 Maybe using a reminder-bot ;) 12:16:42 Action item for next week: put on a shirt. 12:16:47 some weeks tend to be like that :-/ 12:16:59 lol 12:17:00 Hopefully for only the remotee's ;) 12:17:12 Could be a problem in the office :p 12:17:16 JustinClift1, ;) 12:17:20 JustinClift1: TMI. ;) 12:17:27 * ndevos is wearing a shirt that says "there is no cloud, only other peoples computers" 12:17:28 :D 12:17:42 #topic Gluster 3.7 12:17:42 * JustinClift1 is wearing Gluster t-shit :p 12:17:46 shirt 12:17:47 :D 12:18:00 we have a few patches lined up for 3.7.7 12:18:10 http://review.gluster.org/#/q/status:open+branch:+release-3.7 12:18:32 I am working on figuring out who will be release managing 3.7.7 12:18:40 "a few"? 12:19:00 expect 3.7.7 to be out in the next 2 weeks or so 12:19:10 ndevos: anything < 100 is "a few" 12:19:54 was there someone who proposed to be the 3.7.7 release manager? 12:20:00 3.7.7 could be the first release that we put through the minor release test criterion 12:20:33 ndevos: I am working on that, expect an update next week. 12:20:53 maybe we could even run that on the CentOS structure? I've already got 5 volunteers that are interested in setting up tests 12:21:07 ndevos: fantastic, let us do that! 12:21:11 *CentOS Jenkins infrastructure 12:21:46 any other questions, thoughts on 3.7? 12:22:16 figure not, moving on 12:22:22 #topic Gluster 3.6 12:22:30 raghu: updates here? 12:24:07 raghu doesn't seem to be around atm 12:24:25 packages for 3.6.7 were built last week, I don't remember seeing an announcement 12:24:38 will ping raghu about the announcement 12:24:48 #action raghu to announce 3.6.7 GA 12:24:52 moving on 12:24:56 #topic Gluster 3.5 12:25:02 ndevos: any updates here? 12:25:09 I have made 3.6.7 and have announced it 12:25:16 2 patches have been backported, not merged yet 12:25:32 a 3.5.7 is within reach :) 12:25:39 raghu: ok, thanks. that AI is null and void then ;) 12:25:53 ndevos: cool, in the next week or two? 12:26:17 http://www.gluster.org/pipermail/gluster-devel/2015-December/047260.html 12:26:19 hagarth: need to check the release schedule, I thought around the 10th 12:26:48 hagarth: I wanted to create the tracker bug for 3.6.8. But that field is not there in bugzilla 12:26:56 raghu: thank you! 12:26:59 ndevos: right 12:27:21 raghu: will help you get that done 12:27:38 #info 3.5.7 expected around 10th of December 12:27:44 anything else on 3.5? 12:28:01 I dont think so 12:28:06 ok, let us move on 12:28:10 #topic Gluster 3.8 12:28:43 I have setup a meeting tomorrow at the same time to check status of features lined up for 3.8 12:29:12 * ndevos missed the invite? 12:29:15 if you intend to get a feature of yours in 3.8, please be there and help arrive at a release schedule for 3.8 12:29:28 ndevos: sent a heads up, invite to follow 12:29:38 hagarth: ah, ok 12:30:08 oh, right, in the "3.8 update" email from November 30 12:30:23 any questions, comments on 3.8? 12:30:32 ndevos: right :) 12:31:20 hagarth, we are yet to review the ipv6 fix patch sent by Nithin 12:31:20 figure not, let us move on 12:31:32 hagarth, mark that as an action item on me/kshlm 12:31:37 atinm: oh ok, is it passing all tests now? 12:31:48 atinm: thanks! 12:31:49 hagarth, yes it has passed all the tests 12:32:00 #action atinm, kshlm to review IPv6 patchset 12:32:24 anything else on 3.8? 12:32:54 figure not, moving on 12:33:02 #topic Gluster 4.0 12:33:42 Everybody's hacking away, should have a lot to show in a week and a half. 12:34:22 jdarcy: fantastic! 12:34:23 I'm going to run some performance tests on the journal code soon, on all of NSR a bit after that. 12:34:27 We also have the road map page for 4.0 live in gluster.org 12:34:28 https://www.gluster.org/community/roadmap/4.0/ 12:35:18 atinm: looks like a great start, thank you! 12:35:30 From GlusterD 2.0 perspective we need more eyes on ReST APIs and design doc which are available at https://github.com/gluster/glusterd2/wiki 12:35:36 atinm: nice! could you make sure the designs land in the glusterfs-specs repo soon, and update the links when done? 12:36:15 The glusterfs-specs repo is misnamed. It seems to be feature pages, not specs. 12:36:37 ndevos, definitely, the idea is to get them matured first and then we can send PR 12:36:42 jdarcy: +1 12:36:46 well, yeah, feature pages and technical designs (of some sort) 12:37:12 atinm: glusterfs-specs is in Gerrit, it allows easy inline commenting :) 12:37:15 Should we create a subdirectory for actual specs? 12:37:37 * ndevos isnt sure about the current structure, except for the in_progress part 12:38:05 jdarcy: maybe do that and rename the repository too? 12:38:31 hagarth: Perhaps. 12:38:32 ndevos, agreed, let me see whether we can send a patch there, but we don't want to work on two different copies for sure 12:39:02 atinm: yeah, I dont like duplicate repositories/wikis for reviewing either ;-) 12:39:37 if you have ideas on what glusterfs-specs should be renamed to, please send out a post on -devel 12:39:46 ok, anything else here? 12:40:22 hagarth, not from my side 12:40:37 ok, moving on 12:40:54 #topic Open Floor 12:41:02 Weekly reminder to announce Gluster attendance of events: https://public.pad.fsfe.org/p/gluster-events 12:41:31 please add yourselves in there if you are attending an event in the near future 12:41:51 REMINDER to put (even minor) interesting topics on https://public.pad.fsfe.org/p/gluster-weekly-news 12:42:05 * ndevos *cough* 12:42:19 ? 12:42:22 I think weekly should become monthly 12:42:45 yeah, at the very least... 12:42:46 we cannot keep up the frequency of weekly/bi-weekly amidst all other things we do. 12:43:14 I will post an update for November by this weekend 12:43:37 #action hagarth to post Gluster Monthly News this week 12:43:39 thanks hagarth! 12:43:47 hagarth, thanks 12:43:56 would that be something amye could be doing too? 12:43:59 hagarth, I can take it up for next month then 12:44:09 atinm: great, thank you! 12:44:15 If we didn't already discuss it, 3.6.7 {Fedora,EPEL} RPMs and Debian .debs are on d.g.o. Ubuntu .debs are in Launchpad. 12:44:58 and in the CentOS Storage SIG repository that you get when you "yum install centos-release-gluster36" 12:45:00 Kudos to MS and Hari for doing the Ubuntu and Debian builds. 12:45:09 kkeithley: thank you! we mentioned about availability of packages in the 3.6 update. 12:45:24 fantastic, lots of goodness everywhere 12:45:38 kkeithley has setup an etherpad for backports - https://public.pad.fsfe.org/p/gluster-backport-requests 12:45:49 please add your backport requests there 12:46:19 I think developers are advanced users should file a bug instead? 12:46:20 kkeithley: maybe we should drop a note on gluster-users too about the availability of this etherpad? 12:46:32 kkeithley, you are welcome and thanks for your help while helping me build :) 12:46:40 and someone will go through that etherpad and make sure there are bugs for the requested backports? 12:47:02 ndevos: agree, maybe we should provide a flowchart for the backport request process :) 12:47:11 Didn't I send an email already? I'll send (another) one. 12:47:38 we do have something about backports in the docs, not sure how user oriented that is 12:47:43 ndevos: track that here or in the bug triage meeting? 12:48:22 hagarth: the process for requesting backports through bugzilla should be clear, the rest can be handled here 12:48:49 Not everyone can edit the tracker BZ. Editing the wiki was too high a barrier I guess, and nobody seemed to ever look at it. 12:49:41 nobody needs to edit a tracker bz? just file a bug against the version that needs the backport, and point to the upstream bug or patch(es) it needs 12:50:19 ndevos, kkeithley: can we do a poll on the -users list to see what the community would prefer? 12:51:12 I guess someone suggested the etherpad already? we just need to make sure some people watch it and file bugs based on that 12:52:09 ndevos: ok 12:52:31 kkeithley: you and who else is checking the etherpad regulary? 12:52:41 or, is there a way to get notifications on updates? 12:54:17 ndevos: let us discuss more about this in #gluster-dev? 12:54:19 I don't know of a way to get notices. The release manager is responsible for the backports. Filing bugs without updating the tracker seemed (to me) to be the backport graveyard. 12:54:34 I don't know of a way to get notices from the etherpad. 12:55:19 kkeithley: anyone who files a bug can set the "blocks" field to the tracker, but release managers should also check for newly filed bugs against their release 12:55:44 just like developers working on components should check for new bugs against the components they work on 12:56:22 I agree with all those things. ;-) 12:56:51 so what do we need - who does the conversion from etherpad to bugzilla? 12:57:12 and I dont object that we add an other source for reporting issues, but we need a few people that keep an eye on it :) 12:58:08 ndevos, kkeithley: we seem to be running out of time now. let us converge on the process in #gluster-dev. 12:58:18 sure! 12:58:21 any other topics for today? 12:59:03 figure not 12:59:14 thank you all for being here today. talk to you next week! 12:59:18 #endmeeting