On Thu, Mar 15, 2018 at 9:45 AM, Vijay Bellur wrote:
>
>
> On Wed, Mar 14, 2018 at 5:40 PM, Shyam Ranganathan
> wrote:
>
>> On 03/14/2018 07:04 PM, Joe Julian wrote:
>> >
>> >
>> > On 03/14/2018 02:25 PM, Vijay Bellur wrote:
>> >>
>> >>
>> >> On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
>>
On Thu, Mar 15, 2018 at 9:45 AM, Vijay Bellur wrote:
>
>
> On Wed, Mar 14, 2018 at 5:40 PM, Shyam Ranganathan
> wrote:
>
>> On 03/14/2018 07:04 PM, Joe Julian wrote:
>> >
>> >
>> > On 03/14/2018 02:25 PM, Vijay Bellur wrote:
>> >>
>> >>
>> >> On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
>>
On Wed, Mar 14, 2018 at 5:40 PM, Shyam Ranganathan
wrote:
> On 03/14/2018 07:04 PM, Joe Julian wrote:
> >
> >
> > On 03/14/2018 02:25 PM, Vijay Bellur wrote:
> >>
> >>
> >> On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
> >> mailto:kkeit...@redhat.com>> wrote:
> >>
> >> On 03/12/2018 02:3
On 03/14/2018 07:04 PM, Joe Julian wrote:
>
>
> On 03/14/2018 02:25 PM, Vijay Bellur wrote:
>>
>>
>> On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
>> mailto:kkeit...@redhat.com>> wrote:
>>
>> On 03/12/2018 02:32 PM, Shyam Ranganathan wrote:
>> > On 03/12/2018 10:34 AM, Atin Mukherjee
On 03/14/2018 02:25 PM, Vijay Bellur wrote:
On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
mailto:kkeit...@redhat.com>> wrote:
On 03/12/2018 02:32 PM, Shyam Ranganathan wrote:
> On 03/12/2018 10:34 AM, Atin Mukherjee wrote:
>> *
>>
>> After 4.1, we wan
On Tue, Mar 13, 2018 at 4:25 AM, Kaleb S. KEITHLEY
wrote:
> On 03/12/2018 02:32 PM, Shyam Ranganathan wrote:
> > On 03/12/2018 10:34 AM, Atin Mukherjee wrote:
> >> *
> >>
> >> After 4.1, we want to move to either continuous numbering (like
> >> Fedora), or time based (like u
On 03/14/2018 05:38 PM, Shyam Ranganathan wrote:
On 03/14/2018 02:40 AM, Aravinda wrote:
I have following suggestion for managing release notes. Let me know
if this can be included in automation document.
Aravinda, I assume this is an additional suggestion, orthogonal to the
current discussion
We could stand to use our words better on this stuff. Even though we've
thought about it a lot, it's not always clear about what we mean in the
roles and responsibilities.
I'll put a ticket into the Community Working Group to use more words about
this.
- amye
On Wed, Mar 14, 2018 at 8:29 AM, Ragha
On Wed, Mar 14, 2018 at 8:27 PM, Amye Scavarda wrote:
> Responding on the architects question:
>
> On Tue, Mar 13, 2018 at 9:57 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Tue, Mar 13, 2018 at 4:26 PM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>>
>
Responding on the architects question:
On Tue, Mar 13, 2018 at 9:57 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> On Tue, Mar 13, 2018 at 4:26 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Tue, Mar 13, 2018 at 1:51 PM, Amar Tumballi
>> wrote:
>>
>>>
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-14-f32f85c4
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
On 03/14/2018 02:40 AM, Aravinda wrote:
> I have following suggestion for managing release notes. Let me know
> if this can be included in automation document.
Aravinda, I assume this is an additional suggestion, orthogonal to the
current discussion around spec and docs, right?
>
>
> If a Githu
When the test works it takes less than 60 seconds. If it needs more than
200 seconds, that means there's an actual issue.
On Wed, Mar 14, 2018 at 10:16 AM, Raghavendra Gowdappa
wrote:
> All,
>
> I was trying to debug a regression failure [1]. When I ran test locally on
> my laptop, I see some wa
On 03/14/2018 07:13 AM, Shyam Ranganathan wrote:
The Gluster community celebrates 13 years of development with this
latest release, Gluster 4.0. This release enables improved integration
with containers, an enhanced user experience, and a next-generation
management framework. The 4.0 release help
14 matches
Mail list logo
