Forwarded for posterity and follow-up.
Forwarded Message
Subject:Re: GlusterFS removal from Openstack Cinder
Date: Fri, 05 May 2017 21:07:27 +
From: Amye Scavarda
To: Eric Harney , Joe Julian ,
Vijay
On 05/24/2017 12:21 PM, Amar Tumballi wrote:
On Wed, May 24, 2017 at 7:16 PM, Shyam > wrote:
On 05/24/2017 02:05 AM, Amar Tumballi wrote:
Was looking at Milestone in Github:
On Wed, May 24, 2017 at 7:16 PM, Shyam wrote:
> On 05/24/2017 02:05 AM, Amar Tumballi wrote:
>
>> Was looking at Milestone in Github:
>> https://github.com/gluster/glusterfs/issues?q=is%3Aopen+is%
>> 3Aissue+milestone%3A%22Release+3.11+%28STM%29%22
>>
>> It is still showing
Sorry about missing it. Didn't add this event on calendar, and hence
missed. Will be there from next IRC meet.
-Amar
On Wed, May 24, 2017 at 9:28 PM, Kaushal M wrote:
> Very poor turnout today, just 3 attendees including me.
>
> But, we actually did have a discussion and
Very poor turnout today, just 3 attendees including me.
But, we actually did have a discussion and came out with a couple of AIs.
The logs and minutes are available at the links below.
Archive: https://github.com/gluster/glusterfs/wiki/Community-Meeting-2017-05-24
Minutes:
On 05/24/2017 02:05 AM, Amar Tumballi wrote:
Was looking at Milestone in Github:
https://github.com/gluster/glusterfs/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.11+%28STM%29%22
It is still showing many things as open. I see some of them are done for
sure. Please feel free to mark
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-05-24-0bcf9143
___
Gluster-devel mailing list
Gluster-devel@gluster.org
All patches which are more than 60days old:
https://hackmd.io/GYIwhsEMYOwLQGYAMBOATHALCmm4oEZgBTOGYgVgA5qxiqqY0g==#
AFR patches :
https://hackmd.io/BwTgbARgTAJmDMBaeVgDNEBYzAIaJFxhgPELRHlwHYBGMIA=
DHT patches :
https://hackmd.io/EYNg7AZghsUMYFoQBNkGYEBYCMICcCAHJmiAnsnttgEwAMemdEcQA===
All,
Below is mainly a proposal, and I would like to hear people's thought on
these.
- Over the years, we have added many test cases to our regression test
suite, and currently the testing time stands at ~5hrs for 1 patch. But the
current way of '*.t' based regression can't be called
Was looking at Milestone in Github:
https://github.com/gluster/glusterfs/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.11+%28STM%29%22
It is still showing many things as open. I see some of them are done for
sure. Please feel free to mark them as 'Closed'. Ideal to have commit id
(from
10 matches
Mail list logo