On 03/26/2018 12:33 AM, Aravinda wrote:
>>> Also want to propose that, we include a release
>>> of http://github.com/gluster/gluster-health-report with 4.1, and make
>>> the project more usable.
>> In the theme of including sub-projects that we want to highlight, what
>> else should we tag a relea
On 03/23/2018 09:18 AM, Niels de Vos wrote:
> On Fri, Mar 23, 2018 at 10:17:28AM +0530, Amar Tumballi wrote:
>> On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan
>> wrote:
>>
>>> On 03/21/2018 04:12 AM, Amar Tumballi wrote:
Current 4.1 project release lane is empty! I cleaned it up, bec
On 03/22/2018 11:34 PM, Shyam Ranganathan wrote:
On 03/21/2018 04:12 AM, Amar Tumballi wrote:
Current 4.1 project release lane is empty! I cleaned it up, because I
want to hear from all as to what content to add, than add things marked
with the 4.1 milestone by default.
I would
On Fri, Mar 23, 2018 at 10:17:28AM +0530, Amar Tumballi wrote:
> On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan
> wrote:
>
> > On 03/21/2018 04:12 AM, Amar Tumballi wrote:
> > > Current 4.1 project release lane is empty! I cleaned it up, because I
> > > want to hear from all as to wh
On Thu, Mar 22, 2018 at 11:34 PM, Shyam Ranganathan
wrote:
> On 03/21/2018 04:12 AM, Amar Tumballi wrote:
> > Current 4.1 project release lane is empty! I cleaned it up, because I
> > want to hear from all as to what content to add, than add things
> marked
> > with the 4.1 milestone
On 03/21/2018 04:12 AM, Amar Tumballi wrote:
> Current 4.1 project release lane is empty! I cleaned it up, because I
> want to hear from all as to what content to add, than add things marked
> with the 4.1 milestone by default.
>
>
> I would like to see we have sane default values for
Hi Shyam,
Myself and Sunny are working on snapshot integration effort to gd2. So
we wanted to propose the feature for 4.1,
issue : https://github.com/gluster/glusterd2/issues/461
status : There are were two patch sets targeted, one is merged, one is
under review. One is under development.
Rega
On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan
wrote:
> Hi,
>
> As we wind down on 4.0 activities (waiting on docs to hit the site, and
> packages to be available in CentOS repositories before announcing the
> release), it is time to start preparing for the 4.1 release.
>
> 4.1 is where we ha
Sorry, couldn't respond earlier.
On Fri, Mar 16, 2018 at 7:14 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> 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 <
>> pka
Proposing efforts of adding metrics to various perf xlators. Following are
links to github issues:
https://github.com/gluster/glusterfs/issues/422
https://github.com/gluster/glusterfs/issues/423
https://github.com/gluster/glusterfs/issues/424
https://github.com/gluster/glusterfs/issues/425
https:/
On 03/14/2018 12:05 PM, Aravinda wrote:
> 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 addition
I would like to turn features.sdfs on by default starting from 4.1. Details
can be found in issue:
https://github.com/gluster/glusterfs/issues/421
On Fri, Mar 16, 2018 at 1:00 PM, Xavi Hernandez wrote:
> On Tue, Mar 13, 2018 at 2:37 AM, Shyam Ranganathan
> wrote:
>
>> Hi,
>>
>> As we wind down
On Tue, Mar 13, 2018 at 2:37 AM, Shyam Ranganathan
wrote:
> Hi,
>
> As we wind down on 4.0 activities (waiting on docs to hit the site, and
> packages to be available in CentOS repositories before announcing the
> release), it is time to start preparing for the 4.1 release.
>
> 4.1 is where we ha
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:
>>
>>>
>
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:
>>
>>>
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
On 03/13/2018 04:00 PM, Shyam Ranganathan wrote:
On 03/13/2018 03:53 AM, Sankarshan Mukhopadhyay wrote:
On Tue, Mar 13, 2018 at 1:05 PM, Pranith Kumar Karampuri
wrote:
On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan
wrote:
Hi,
As we wind down on 4.0 activities (waiting on docs to hit th
On Wed, Mar 14, 2018 at 10:27 AM, 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:
>>
>>> >>
>> Further, as we hit end of Ma
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:
>
>> >>
>>> >> Further, as we hit end of March, we would make it mandatory for
>>> features
>>> >> to have required spec and doc labels, before the
On Tue, Mar 13, 2018 at 1:51 PM, Amar Tumballi wrote:
> >>
>> >> Further, as we hit end of March, we would make it mandatory for
>> features
>> >> to have required spec and doc labels, before the code is merged, so
>> >> factor in efforts for the same if not already done.
>> >
>> >
>> > Could you
On 03/13/2018 03:53 AM, Sankarshan Mukhopadhyay wrote:
> On Tue, Mar 13, 2018 at 1:05 PM, Pranith Kumar Karampuri
> wrote:
>>
>>
>> On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan
>> wrote:
>>>
>>> Hi,
>>>
>>> As we wind down on 4.0 activities (waiting on docs to hit the site, and
>>> packages
>
> >>
> >> Further, as we hit end of March, we would make it mandatory for features
> >> to have required spec and doc labels, before the code is merged, so
> >> factor in efforts for the same if not already done.
> >
> >
> > Could you explain the point above further? Is it just the label or the
>
On Tue, Mar 13, 2018 at 1:05 PM, Pranith Kumar Karampuri
wrote:
>
>
> On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan
> wrote:
>>
>> Hi,
>>
>> As we wind down on 4.0 activities (waiting on docs to hit the site, and
>> packages to be available in CentOS repositories before announcing the
>> rel
On Tue, Mar 13, 2018 at 7:07 AM, Shyam Ranganathan
wrote:
> Hi,
>
> As we wind down on 4.0 activities (waiting on docs to hit the site, and
> packages to be available in CentOS repositories before announcing the
> release), it is time to start preparing for the 4.1 release.
>
> 4.1 is where we ha
27 matches
Mail list logo