Following up on this, this revision cycle is meant to be more clear about
owners + peers, and less focused on the Red Hat shorthand for levels of
responsibility.
As far as further goals, I think we can outline Architects and Leads
responsibility in a further cycle. I'll let Vijay respond to a furt
On Fri, Apr 14, 2017 at 2:40 AM, Michael Scherer
wrote:
> Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :
> > In light of community conversations, I've put some revisions on the
> > Maintainers changes, outlined in the hackmd pad:
> > https://hackmd.io/s/SkwiZd4qe
> >
> > Feedback w
On 04/17/2017 05:56 AM, Poornima Gurusiddaiah wrote:
Further to the above, we are also considering the following features for
this release, request feature owners to let us know if these are
actively being worked on and if these will make the branching dates.
(calling out folks that I think are t
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-04-17-a9b5333d
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
h
On Mon, Apr 17, 2017 at 12:48 AM, Nigel Babu wrote:
> This should be fixed now: https://bugzilla.redhat.com/sh
> ow_bug.cgi?id=1442672
>
Thank you Nigel.
>
>
> Vijay, can you link me to your failed Jenkins job? Jenkins should have
> been able to clone since it uses the git protocol and not
- Original Message -
> From: "Shyam"
> To: "Gluster Devel"
> Cc: gluster-us...@gluster.org
> Sent: Thursday, April 13, 2017 8:17:34 PM
> Subject: Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and
> feature tracking
>
> On 02/28/2017 10:17 AM, Shyam wrote:
> > Hi,
> >
>
