Re: [Gluster-devel] Reducing merge conflicts

Completely agree with your concern here. Keeping aside the regression part, few observations and suggestions: As per the Maintainers guidelines (https://gluster.readthedocs.io/en/latest/Contributors-Guide/Guidelines-For-Maintainers/): a> Merge patches of owned components only. b> Seek

Re: [Gluster-devel] Reducing merge conflicts

- Original Message - > From: "Pranith Kumar Karampuri" > To: "Jeff Darcy" > Cc: "Gluster Devel" > Sent: Friday, July 8, 2016 9:28:57 AM > Subject: Re: [Gluster-devel] Reducing merge conflicts > > > > On Fri, Jul 8,

Re: [Gluster-devel] iSCSI

Prasanna - Can you help here? ~Atin On Fri, Jul 8, 2016 at 3:51 AM, francis Lavalliere < francis.lavalli...@gmail.com> wrote: > Hello, > > I've been messing around with Gluster FS version 3.7 and 3.8. > > Currently i am trying to implement iSCSI with Gluster FS. > > I've installed ubuntu 16.04

Re: [Gluster-devel] [Gluster-Maintainers] Glusterfs-3.7.13 release plans

Could you take in http://review.gluster.org/#/c/14598/ as well? It is ready for merge. On Thu, Jul 7, 2016 at 3:02 PM, Atin Mukherjee wrote: > Can you take in http://review.gluster.org/#/c/14861 ? > > > On Thursday 7 July 2016, Kaushal M wrote: > >> On

Re: [Gluster-devel] Reducing merge conflicts

On Fri, Jul 8, 2016 at 8:40 AM, Jeff Darcy wrote: > > What gets measured gets managed. > > Exactly. Reviewing is part of everyone's job, but reviews aren't tracked > in any way that matters. Contrast that with the *enormous* pressure most > of us are under to get our own

Re: [Gluster-devel] Reducing merge conflicts

+Nigel On Fri, Jul 8, 2016 at 7:42 AM, Pranith Kumar Karampuri wrote: > What gets measured gets managed. It is good that you started this thread. > Problem is two fold. We need a way to first find people who are reviewing a > lot and give them more karma points in the

Re: [Gluster-devel] Reducing merge conflicts

> What gets measured gets managed. Exactly. Reviewing is part of everyone's job, but reviews aren't tracked in any way that matters. Contrast that with the *enormous* pressure most of us are under to get our own patches in, and it's pretty predictable what will happen. We need to change that

Re: [Gluster-devel] Reducing merge conflicts

What gets measured gets managed. It is good that you started this thread. Problem is two fold. We need a way to first find people who are reviewing a lot and give them more karma points in the community by encouraging that behaviour(making these stats known to public lets say in monthly news

[Gluster-devel] iSCSI

Hello, I've been messing around with Gluster FS version 3.7 and 3.8. Currently i am trying to implement iSCSI with Gluster FS. I've installed ubuntu 16.04 and have installed various components: I didnt found any tcmu-runner packages for ubuntu, so i manually built it using their git

[Gluster-devel] Reducing merge conflicts

I'm sure a lot of you are pretty frustrated with how long it can take to get even a trivial patch through our Gerrit/Jenkins pipeline. I know I am. Slow tests, spurious failures, and bikeshedding over style issues are all contributing factors. I'm not here to talk about those today. What I

Re: [Gluster-devel] [PATCH v2 1/1] block/gluster: add support to choose libgfapi logfile

On Thu, Jul 07, 2016 at 01:43:50AM +0530, Prasanna Kumar Kalever wrote: > currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded > in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE > gfapi logs will be huge and fill/overflow the console view. >

[Gluster-devel] Preparing to release glusterfs-3.8.1

Hi, The tagging and release of glusterfs-3.8.1 is scheduled for tomorrow morning (Friday morning, in Amsterdam). There are still some patches under review, but until they have at least a +1 from an additional developer that is familiar with the component I'm not merging them. Maintainers of the

Re: [Gluster-devel] [Gluster-Maintainers] Glusterfs-3.7.13 release plans

Can you take in http://review.gluster.org/#/c/14861 ? On Thursday 7 July 2016, Kaushal M wrote: > On Thu, Jun 30, 2016 at 11:08 AM, Kaushal M > wrote: > > Hi all, > > > > I'm (or was) planning to do a 3.7.13 release on schedule today.

Re: [Gluster-devel] Glusterfs-3.7.13 release plans

On Thu, Jun 30, 2016 at 11:08 AM, Kaushal M wrote: > Hi all, > > I'm (or was) planning to do a 3.7.13 release on schedule today. 3.7.12 > has a huge issue with libgfapi, solved by [1]. > I'm not sure if this fixes the other issues with libgfapi noticed by > Lindsay on

[Gluster-devel] GlusterFS linux-AIO bug

hi, I have some problems about linux-AIO. I have installed GlusterFS 3.6.7 because of its stability, and mounted to /mnt/glusterfs. When I excute "vi /mnt/glusterfs/test.txt", it was ok and I wrote something successfully. But when I changed the code in

[Gluster-devel] Updating Jenkins with Jenkins

Hello folks, As you have read from my emails over this month, I'm going to have Jenkins jobs generated from JJB. I'm going to go one step further. I'm going to move the repo[1] into Gerrit. One successful merge on Gerrit, it will update Jenkins. I'll do a sync from Gerrit to Github for this repo.