Congrats Xavi!
On Sun, Sep 6, 2015 at 5:07 PM, Atin Mukherjee wrote:
> Congrats Xavi!!
>
> ~Atin
>
> On 09/04/2015 06:56 PM, Xavier Hernandez wrote:
>> Hi all,
>>
>> I've recently become father and the child keeps me quite busy, so I
>> won't be much available until I return
Did we just have 3 releases of 3.6.7?
On Wed, Nov 25, 2015 at 5:49 PM, Gluster Build System
wrote:
>
>
> SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.6.7.tar.gz
>
> This release is made off jenkins-release-147
>
> -- Gluster Build System
>
The gerrit-trigger plugin which automatically triggered jobs is
temporarily not working. We are trying to find out why and will fix it
soon.
In the mean time maintainers who need tests to run immediately, can
manually trigger jobs. To manually trigger jobs,
1. Get the REFSPEC of the change from
On Sat, Nov 21, 2015 at 4:45 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Fri, Nov 20, 2015 at 10:13 PM, Vijay Bellur <vbel...@redhat.com> wrote:
>>
>>
>> - Original Message -
>>> From: "Kaushal M" <kshlms...@gmail.com>
>
On Thu, Jun 9, 2016 at 12:13 PM, Kaushal M <kshlms...@gmail.com> wrote:
> A heads up to all maintainers and developers.
>
> As all of you probably already know, reviews in Gerrit are getting
> random votes for jobs that ran for other patchsets.
>
> We've had people notici
On Sat, May 7, 2016 at 2:07 PM, Niels de Vos wrote:
> Hi,
>
> with the close to getting released 3.8, I would like to make sure that
> we do not start to backport features and make invasive changes. This
> should ensure us that most developers work on the next version with a
>
On Fri, Jun 10, 2016 at 6:39 AM, Niels de Vos <nde...@redhat.com> wrote:
> On Wed, Jun 08, 2016 at 07:12:12PM +0530, Kaushal M wrote:
>> On Sat, May 7, 2016 at 2:07 PM, Niels de Vos <nde...@redhat.com> wrote:
>> > Hi,
>> >
>> > with the close to
Hi all,
If anyone doesn't know about it yet, the release process for a release
has changed. Refer to the mail thread [1] for more information.
tl;dr, component maintainers need to now provide an acknowledgement
that their component is ready to the release manager, for the manager
to make the
.
~kaushal
-- Forwarded message --
From: Kaushal M <kshlms...@gmail.com>
Date: Thu, Jun 9, 2016 at 11:52 AM
Subject: Investigating random votes in Gerrit
To: gluster-infra <gluster-in...@gluster.org>
In addition to the builder issues we're having, we are also fac
On Wed, Jun 15, 2016 at 7:37 PM, Kaushal M <kshlms...@gmail.com> wrote:
> Hi all,
>
> If anyone doesn't know about it yet, the release process for a release
> has changed. Refer to the mail thread [1] for more information.
>
> tl;dr, component maintainers need to now pr
On Thu, Jun 23, 2016 at 3:47 PM, Raghavendra Gowdappa
<rgowd...@redhat.com> wrote:
>
>
> - Original Message -
>> From: "Raghavendra Gowdappa" <rgowd...@redhat.com>
>> To: "Kaushal M" <kshlms...@gmail.com>
>> Cc: mai
On Fri, Jun 24, 2016 at 3:09 PM, Raghavendra Gowdappa
<rgowd...@redhat.com> wrote:
>
>
> - Original Message -
>> From: "Kaushal M" <kshlms...@gmail.com>
>> To: "Raghavendra Gowdappa" <rgowd...@redhat.com>
>> Cc: maintainers
On Thu, Jan 14, 2016 at 5:12 PM, Niels de Vos <nde...@redhat.com> wrote:
> On Thu, Jan 14, 2016 at 03:46:02PM +0530, Kaushal M wrote:
>> On Thu, Jan 14, 2016 at 2:43 PM, Niels de Vos <nde...@redhat.com> wrote:
>> > On Thu, Jan 14, 2016 at 11:51:15AM +0530, Raghave
On Mon, Jan 18, 2016 at 1:03 PM, Raghavendra Talur <rta...@redhat.com> wrote:
>
>
> On Fri, Jan 15, 2016 at 4:22 PM, Niels de Vos <nde...@redhat.com> wrote:
>>
>> On Thu, Jan 14, 2016 at 10:26:46PM +0530, Kaushal M wrote:
>> > I'd pushed the
On Mon, Jun 27, 2016 at 11:40 PM, Kaleb S. KEITHLEY wrote:
> On 06/24/2016 07:26 AM, Gluster Build System wrote:
>>
>>
>> SRC:
>> http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.12.tar.gz
>>
>> This release is made off jenkins-release-162
>
> Packages of
eview.gluster.org/14710
> http://review.gluster.org/14637
>
> I will acknowledge the working of Geo-replication components with the above
> mentioned patches. Let me know if that is fine.
>
> regards
> Aravinda
>
>
> On 06/15/2016 07:37 PM, Kaushal M wrote:
>>
>>
Hi All.
Raghavendra had volunteered to be the release manager last week. But
unfortunately, he cannot find enough time in the next couple of weeks
(because of other work commitments) to perform the manager tasks.
So we now need a volunteer to be the new release manager. Anyone?
Keep in mind,
Hey Raghu,
Now that the patch submission issues are solved, could you provide an
update on 3.6.9. We're past the 20th now.
~kaushal
On Wed, Feb 17, 2016 at 7:18 PM, Kaushal M <kshlms...@gmail.com> wrote:
> I'm online now. We can figure out what the problem is.
>
> On Feb 17, 201
Bellur" <vbel...@redhat.com
>>> <mailto:vbel...@redhat.com>> wrote:
>>> >
>>> > On 02/24/2016 07:20 AM, Kaushal M wrote:
>>> >>
>>> >> Hi All.
>>> >>
>>> >> Raghavendra had volunteered to be the relea
Hey Johnny,
Could you please provide an update on the 3.6.9 release plans?
The GlusterFS release schedule has 3.6 releases happening every month
on the week of the 20th. We're less than a week away to the release as
per the schedule, so we'd like to know if it is still on track.
Thanks.
gets submitted. I need some help in
> resolving it.
>
> Regards,
> Raghavendra
>
>
> On Wed, Feb 17, 2016 at 8:31 AM, Kaushal M <kshlms...@gmail.com> wrote:
>
>> Hey Johnny,
>>
>> Could you please provide an update on the 3.6.9 release plans?
Hey Johnny,
Could you please do the bugzilla cleanup for the 3.6.9 release (close
bugs, close tracker) and open the 3.6.10 tracker?
This hasn't been done yet, and should be performed when announcing a release.
Thanks.
On Fri, Mar 4, 2016 at 9:02 PM, FNU Raghavendra Manjunath
On Thu, Apr 7, 2016 at 5:11 PM, Kaushal M <kshlms...@gmail.com> wrote:
> We've hit another regression.
>
> With management encryption enabled, daemons like NFS and SHD don't
> start on the current heads of release-3.7 and master branches.
>
> I still have no clear root
On Thu, Apr 7, 2016 at 7:24 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Thu, Apr 7, 2016 at 6:23 PM, Kaushal M <kshlms...@gmail.com> wrote:
>> On Thu, Apr 7, 2016 at 6:00 PM, Atin Mukherjee <amukh...@redhat.com> wrote:
>>>
>>>
>>> On 04
On 7 Apr 2016 5:36 p.m., "Niels de Vos" <nde...@redhat.com> wrote:
>
> On Thu, Apr 07, 2016 at 05:13:54PM +0530, Kaushal M wrote:
> > On Thu, Apr 7, 2016 at 5:11 PM, Kaushal M <kshlms...@gmail.com> wrote:
> > > We've hit another regression.
> > &g
I'd rather not take in new changes. Right now my priority is to get
this new regression.
On Thu, Apr 7, 2016 at 5:21 PM, Ravishankar N <ravishan...@redhat.com> wrote:
> On 04/07/2016 05:11 PM, Kaushal M wrote:
>>
>> As earlier, please don't merge any more changes on the relea
On Thu, Apr 7, 2016 at 6:23 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Thu, Apr 7, 2016 at 6:00 PM, Atin Mukherjee <amukh...@redhat.com> wrote:
>>
>>
>> On 04/07/2016 05:37 PM, Kaushal M wrote:
>>>
>>> On 7 Apr 2016 5:36 p.m., "Niels
Hi All,
I'm tagging 3.7.11, so please don't merge anymore changes on the
release-3.7 branch.
I'm currently on commit 458d4ba, which will be tagged as v3.7.11.
I'll notify once the tagging is done, and merging changes can be resumed.
Thanks,
Kaushal
Hello maintainers!
If you didn't know, we have a maintainers guide at [1]. This document
describes what is expected from a GlusterFS maintainer, and is a quick
guide on maintainer-ship.
But this document is very light at the moment, and can be improved.
So, I'd like to know what other
I've added you to the maintainers lists now.
On Wed, Mar 9, 2016 at 11:15 AM, Vijaikumar Mallikarjuna
wrote:
> Hi,
>
> I will be the maintainer for quota and marker component and the same is
> updated in the Maintainer's List.
> Could you please provide merge access to the
next time!
>
> Thanks and Regards,
> Kotresh H R
>
> - Original Message -
>> From: "Kaushal M" <kshlms...@gmail.com>
>> To: "Kotresh Hiremath Ravishankar" <khire...@redhat.com>
>> Cc: "Aravinda" <avish...@redhat.com>,
Hi All,
There has been a recent change which has caused failures to build
RPMs. This change was also unknowingly backported to release-3.7,
because the failures were not reported back to gerrit.
Rpmbuild results aren't being reported back to gerrit since we brought
in the new flags for voting.
On Tue, May 10, 2016 at 12:01 AM, Vijay Bellur wrote:
> Hi All,
>
> We are blocked on 3.7.12 owing to this proposal. Appreciate any
> feedback on this!
>
> Thanks,
> Vijay
>
> On Thu, Apr 28, 2016 at 11:58 PM, Vijay Bellur wrote:
>> Hi All,
>>
>> We have
I've merged this change as it had passed all the jobs, and doesn't
seem (to me) to have any unexpected side effects.
On Sat, Apr 16, 2016 at 7:24 AM, Kaushal M <kshlms...@gmail.com> wrote:
> As I understand it's just a regression in the log messages. Does it
> have any impact on f
h recent fix.
>
> This regression bug has been fixed in master, can we take this patch for
> 3.7.11?
>
> Here is the 3.7 patch: http://review.gluster.org/#/c/13962/
>
> Thanks,
> Vijay
>
>
> On Thu, Apr 7, 2016 at 10:14 AM, Kaushal M <kshlms...@gmail.com> wrote:
>
Some more (bad) news on the status of 3.7.11.
I've been doing some more tests with release-3.7, and found that the
fix for solving daemons failing to start when management encryption is
enabled doesn't work in all cases.
Now I've got 2 options I can take, and would like some opinions on
which I
On Fri, Apr 15, 2016 at 2:36 PM, Niels de Vos <nde...@redhat.com> wrote:
> On Fri, Apr 15, 2016 at 01:32:23PM +0530, Kaushal M wrote:
>> Some more (bad) news on the status of 3.7.11.
>>
>> I've been doing some more tests with release-3.7, and found that the
>>
Hi all,
3.7.14 is scheduled to be tagged on the 30th of this month
(30/Jul/2016), ie. in 3 more days.
Please ensure that you get the required changes merged by 1200 UTC on the 30th.
We have a good amount of fixes already with 18 commits into
release-3.7 since 3.7.13.
Make sure to add bugs for
the RCA). Do we want to include this in 3.7.13?
I'm not going to be delaying the release anymore. I'll be adding this
issue into the release-notes as a known-issue.
>
> regards,
> Raghavendra.
>
> ----- Original Message -
>> From: "Kaushal M" <kshlm
On Sat, Jul 9, 2016 at 10:02 PM, Atin Mukherjee wrote:
> We have hit a bug 1347250 in downstream (applicable upstream too) where it
> was seen that glusterd didnt regenerate the volfiles when it was interimly
> brought up with upgrade mode by yum. Log file captured that
t;>
>> Can you take in http://review.gluster.org/#/c/14861 ?
Can you get one of the maintainers to give it a +2?
>>
>>
>> On Thursday 7 July 2016, Kaushal M <kshlms...@gmail.com> wrote:
>>>
>>> On Thu, Jun 30, 2016 at 11:08 AM, Kaushal M <kshlms...@gmail.c
On Tue, Aug 2, 2016 at 2:21 PM, Kaushal M <kshlms...@gmail.com> wrote:
> Hi All.
>
> We've been discussing about improvements to our release process and
> schedules for a while now. As a result of these discussions I had
> started an etherpad [1] to put together a rel
Thanks for the quick builds! This is going to be the fastest release
ever to go from tagging to announcement.
On Mon, Aug 1, 2016 at 10:52 PM, Kaleb S. KEITHLEY wrote:
> On 08/01/2016 02:16 AM, Gluster Build System wrote:
>>
>>
>> SRC:
>>
Hi All.
We've been discussing about improvements to our release process and
schedules for a while now. As a result of these discussions I had
started an etherpad [1] to put together a release process document.
I've created a pull-request [2] to glusterdocs based on this etherpad,
to make it
On Thu, Jun 30, 2016 at 1:57 PM, Niels de Vos <nde...@redhat.com> wrote:
> On Thu, Jun 30, 2016 at 12:46:57PM +0530, Atin Mukherjee wrote:
>> On Thu, Jun 30, 2016 at 11:56 AM, Atin Mukherjee <amukh...@redhat.com>
>> 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-users.
This patch has been included in the packages 3.7.12 built for CentOS,
Hi all,
GlusterFS-3.7.20 is intended to be the final release for release-3.7.
3.7 enters EOL with the expected release of 3.10 in about 2 weeks.
Once 3.10 is released I'll be closing any open bugs on 3.7 and
abandoning any patches on review.
So as the subject says, developers please stop
I'll be tagging this release later today. This should be the final 3.7
release after over a year and half of updates.
~kaushal
___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers
Hi all.
We have 1 more week till the scheduled 30th August release date for
GlusterFS-3.7.15.
Till today, 34 new commits have been merged into release-3.7 since the
tagging of 3.7.14. Gerrit has ~30 open patches on release-3.7 [1],
about 10 of which have been submitted after 3.7.14.
Notify the
Let's try this again.
We are doing a final screening of the 3.6 bug list after the next
bug-triage meeting (1200UTC 23 Aug 2016, ie tomorrow).
All maintainers are requested to attend this meeting and screen bugs
for their components. The list of bugs is available at [1]. Bugs that
have been
Also, remember to edit the rfc.sh script to point to the correct branch.
On Thu, Sep 1, 2016 at 11:40 AM, Kaushal M <kshlms...@gmail.com> wrote:
> You should be pushing to git.gluster.org, not github. Remove the
> `g...@github.com:gluster/glusterfs.git` url from the remote. And
Thanks, Kaleb.
I'll make the announcement now.
On Wed, Aug 31, 2016 at 9:03 PM, Kaleb S. KEITHLEY wrote:
> On 08/30/2016 10:14 AM, Gluster Build System wrote:
>>
>>
>> SRC:
>> http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.15.tar.gz
>>
>> This release is
On Tue, Aug 30, 2016 at 9:16 PM, Niels de Vos wrote:
> On Tue, Aug 30, 2016 at 07:14:48AM -0700, Gluster Build System wrote:
>>
>>
>> SRC:
>> http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.15.tar.gz
>
> Packages for the CentOS Storage SIG have been build for
Hi all,
This is a call for volunteers to manage the 3.7.16 release.
I want to spend some more time on GD2, and so I want to temporarily
give up release management duties.
I'll be available to help with the release process if you are not
clear about it.
~kaushal
On Thu, Sep 8, 2016 at 1:55 PM, Kaushal M <kshlms...@gmail.com> wrote:
> Hi all,
>
> This is a call for volunteers to manage the 3.7.16 release.
>
> I want to spend some more time on GD2, and so I want to temporarily
> give up release management duties.
>
Hi all,
GlusterFS-3.7.16 is on target to be released on Sep 30, 4 days from now.
In preparation for the release, maintainers please stop merging
anymore changes into release-3.7.
If any developer has a change that needs to be merged, please reply to
this email before end of day Sep 28.
At this
of
each other.
If you could confirm before this time tomorrow, I'll take them in.
Thanks,
Kaushal
On Fri, Sep 30, 2016 at 9:00 PM, Niels de Vos <nde...@redhat.com> wrote:
> On Mon, Sep 26, 2016 at 03:08:42PM +0530, Kaushal M wrote:
>> Hi all,
>>
>> GlusterFS-3.7.16
On Thu, Nov 10, 2016 at 1:11 PM, Atin Mukherjee wrote:
>
>
> On Thu, Nov 10, 2016 at 1:04 PM, Pranith Kumar Karampuri
> wrote:
>>
>> I am trying to understand the criticality of these patches. Raghavendra's
>> patch is crucial because gfapi workloads(for
On Fri, Nov 18, 2016 at 1:17 PM, Kaushal M <kshlms...@gmail.com> wrote:
> IMPORTANT: Till this is fixed please stop merging changes into release-3.7
>
> I made a mistake.
>
> When tagging v3.7.17, I noticed that the release-notes at 8b95eba were
> not correct.
> So I cor
On Fri, Nov 18, 2016 at 1:22 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Fri, Nov 18, 2016 at 1:17 PM, Kaushal M <kshlms...@gmail.com> wrote:
>> IMPORTANT: Till this is fixed please stop merging changes into release-3.7
>>
>> I made a mistake.
>
IMPORTANT: Till this is fixed please stop merging changes into release-3.7
I made a mistake.
When tagging v3.7.17, I noticed that the release-notes at 8b95eba were
not correct.
So I corrected it with a new commit, c11131f, directly on top of my
local release-3.7 branch (I'm sorry that I didn't
On Fri, Nov 18, 2016 at 2:04 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Fri, Nov 18, 2016 at 1:22 PM, Kaushal M <kshlms...@gmail.com> wrote:
>> On Fri, Nov 18, 2016 at 1:17 PM, Kaushal M <kshlms...@gmail.com> wrote:
>>> IMPORTANT: Till this is fixed plea
On Fri, Nov 18, 2016 at 3:29 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Fri, Nov 18, 2016 at 2:04 PM, Kaushal M <kshlms...@gmail.com> wrote:
>> On Fri, Nov 18, 2016 at 1:22 PM, Kaushal M <kshlms...@gmail.com> wrote:
>>> On Fri, Nov 18, 2016 at 1:17 PM, K
Pranith,
This change [1] removing experimental xlators isn't merged yet. It
should be taken in before you do your release.
[1]: https://review.gluster.org/15750
On Fri, Nov 11, 2016 at 4:23 PM, Niels de Vos wrote:
> On Thu, Nov 10, 2016 at 04:52:29PM -0500, Kaleb S. KEITHLEY
I'm continuing testing GlusterD for 3.9.0rc2. I wasted a lot of my
time earlier this morning testing 3.8.5 because of an oversight.
I have one issue till now, the cluster.op-version defaults to 4.
This shouldn't be how it's supposed to be. It needs to be set to the
39000 for 3.9.0.
I'll send
Hi all,
This is a reminder to all to add their updates to weekly meeting pad
[1]. Please make sure you find some time to add updates about your
components, features or things you are working on.
Thanks,
Kaushal
[1] https://public.pad.fsfe.org/p/gluster-community-meetings
On Mon, Dec 12, 2016 at 12:35 PM, Niels de Vos wrote:
> On Thu, Dec 08, 2016 at 04:17:59AM -0500, Kaleb Keithley wrote:
>>
>> Packages for Fedora 23 are queued for testing in Bodhi; will land soon in
>> Updates-Testing and then Updates repos.
>> Packages for Fedora 24 and
Daryl, on the gluster-users list, tested out the Storage SIG packages
for 3.8.8 [1]. You can push the packages to release and announce the
release now.
[1]: https://lists.gluster.org/pipermail/gluster-users/2017-January/029667.html
On Wed, Jan 11, 2017 at 10:09 PM, Niels de Vos
On Mon, Jan 9, 2017 at 9:41 PM, Niels de Vos wrote:
> On Mon Jan 9 16:57:02 2017 GMT+0100, Kaleb S. KEITHLEY wrote:
>> On 01/09/2017 01:44 AM, Gluster Build System wrote:
>> >
>> >
>> > SRC:
>> > http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.19.tar.gz
>> >
3.7.19 was supposed to be tagged on 30th December, but didn't happen
due to the holidays.
I'll be tagging the release before the end of this week. To do this,
no more patches will be merged after tomorrows meeting. If anyone has
anything to get merged before then, please bring it to my notice.
I'm okay with the Wednesday and Friday slots.
On Mon, Jul 31, 2017 at 12:36 PM, Amar Tumballi wrote:
> Hi All,
>
> It will be great to have everyone's participation for 4.0 discussions,
> considering it would be significant decision for the project. Hence, having
> a meeting
On Tue, May 2, 2017 at 3:55 PM, Pranith Kumar Karampuri
wrote:
>
>
> On Sun, Apr 30, 2017 at 9:01 PM, Shyam wrote:
>>
>> Hi,
>>
>> Release 3.11 for gluster has been branched [1] and tagged [2].
>>
>> We have ~4weeks to release of 3.11, and a week to
On Thu, May 4, 2017 at 6:40 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Thu, May 4, 2017 at 4:38 PM, Niels de Vos <nde...@redhat.com> wrote:
>> On Thu, May 04, 2017 at 03:39:58PM +0530, Pranith Kumar Karampuri wrote:
>>> On Wed, May 3, 2017 at 2:36 PM, Kaushal
On Thu, May 4, 2017 at 4:38 PM, Niels de Vos <nde...@redhat.com> wrote:
> On Thu, May 04, 2017 at 03:39:58PM +0530, Pranith Kumar Karampuri wrote:
>> On Wed, May 3, 2017 at 2:36 PM, Kaushal M <kshlms...@gmail.com> wrote:
>>
>> > On Tue, May 2, 2017 at 3:55 PM,
Hey all,
We are continuing our development of the core of GD2, and will soon
come to the stage where we can begin integrating and developing other
commands for GD2.
As the GD2 team, we are developing and implementing the core commands
for managing Gluster. These include the basic volume
On 7 Sep 2017 6:25 pm, "Niels de Vos" wrote:
On Thu, Sep 07, 2017 at 04:41:54PM +0530, Nigel Babu wrote:
> On Thu, Sep 07, 2017 at 12:43:28PM +0200, Niels de Vos wrote:
> >
> > Q: Can patches of a series be merged before all patches in the series
> > have a +2? Initial changes
Hi all,
We need a volunteer to stand in as the host of today's community meeting, as
I will not be able to host or attend today's community meeting.
If anyone wants to volunteer, let the rest know by replying here.
Also, reply if you're willing to regularly host/co-host the meetings
as well.
On Fri, Jun 15, 2018 at 6:26 PM Niels de Vos wrote:
>
> On Fri, Jun 15, 2018 at 05:03:38PM +0530, Kaushal M wrote:
> > In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote:
> > >
> > > On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote:
> &g
In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote:
>
> On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote:
> > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > > As brick-mux tests were failing (and still are on master), this was
> > > holding up the release activity.
> > >
>
On Mon, Jun 4, 2018 at 7:05 PM Kaleb S. KEITHLEY wrote:
>
> On 06/02/2018 07:47 AM, Niels de Vos wrote:
> > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote:
> >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> >> wrote:
> >>>
> >&g
On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote:
>
> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > As brick-mux tests were failing (and still are on master), this was
> > holding up the release activity.
> >
> > We now have a final fix [1] for the problem, and the situation has
> >
On Mon, Jun 4, 2018 at 10:55 PM Kaleb S. KEITHLEY wrote:
>
> On 06/04/2018 11:32 AM, Kaushal M wrote:
>
> >
> > We have a proper release this time. Source tarballs are available from [1].
> >
> > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0
&g
On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
>
> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote:
> >
> > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > > As brick-mux tests were failing (and still are on master), this was
> > > holding up
On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote:
>
> On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
> >
> > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> > wrote:
> > >
> > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote:
> > > > As
On Mon, Jun 4, 2018 at 5:29 PM Kaleb S. KEITHLEY wrote:
>
> On 06/02/2018 07:47 AM, Niels de Vos wrote:
> > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote:
> >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> >> wrote:
> >>>
> >&g
On Mon, Jun 4, 2018 at 8:54 PM Kaushal M wrote:
>
> On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote:
> >
> > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote:
> > >
> > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan
> > > wrote:
> > &g
On Mon, Jul 2, 2018 at 6:32 PM Pranith Kumar Karampuri
wrote:
>
>
>
> On Mon, Jul 2, 2018 at 5:01 PM, Amar Tumballi wrote:
>>
>>
>>
>> On Mon, Jul 2, 2018 at 4:51 PM, Nigel Babu wrote:
>>>
>>> This discussion sort of died, so I'm going to propose 1300 UTC and 1500 UTC
>>> on Mondays. If you
On Thu, Jan 11, 2018 at 1:56 AM, Kaleb S. KEITHLEY wrote:
> comments inline
>
> On 01/10/2018 02:08 PM, Shyam Ranganathan wrote:
>
> Hi, (GD2 team, packaging team, please read)
>
> Here are some things we need to settle so that we can ship/release GD2
> along with Gluster 4.0
Hi all,
GlusterD2 v4.0rc0 has been tagged and a release made in anticipation
of GlusterFS-v4.0rc0. The release and source tarballs are available
from [1].
There aren't any sepcific release-notes for this release.
Thanks.
~kaushal
[1]: https://github.com/gluster/glusterd2/releases/tag/v4.0rc0
On Mon, Jun 18, 2018 at 11:30 PM Kaleb S. KEITHLEY wrote:
>
> On 06/18/2018 12:03 PM, Kaushal M wrote:
> >
> > GD2 packages have been built for Fedora 28 and available from the
> > updates-testing repo, and soon from the updates repo
> > Packages are also available
On Thu, Mar 8, 2018 at 10:21 AM, Amar Tumballi wrote:
> Meeting date: 03/07/2018 (March 3rd, 2018. 19:30IST, 14:00UTC, 09:00EST)
>
> BJ Link
>
> Bridge: https://bluejeans.com/205933580
> Download : https://bluejeans.com/s/mOGb7
>
> Attendance
>
> [Sorry Note] : Atin
On Tue, Mar 6, 2018 at 8:59 PM, Shyam Ranganathan wrote:
> On 03/06/2018 10:25 AM, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.tar.gz
>> HASH:
>>
On Tue, Mar 6, 2018 at 9:19 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Tue, Mar 6, 2018 at 8:59 PM, Shyam Ranganathan <srang...@redhat.com> wrote:
>> On 03/06/2018 10:25 AM, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/
On Tue, Oct 23, 2018 at 8:24 PM Kaleb S. KEITHLEY wrote:
>
> On 10/23/18 10:49 AM, Kaleb S. KEITHLEY wrote:
> > On 10/23/18 10:38 AM, Kaushal M wrote:
> >> On Mon, Oct 22, 2018 at 7:41 PM Kaleb S. KEITHLEY
> >> wrote:
> >>>
> >
On Mon, Oct 22, 2018 at 7:41 PM Kaleb S. KEITHLEY wrote:
>
> On 10/22/18 9:29 AM, Shyam Ranganathan wrote:
> >>
> >> @Kaushal, if we tag GA tomorrow EDT, would it be possible to tag GD2
> >> today, for the packaging team to pick the same up?
> >>
> >
> > @GD2 team can someone tag/branch GD2 for
The IPV6 implementation in Gluster requires that IPV6 be enabled in the
kernel and that getaddrinfo works for AF_INET6. This is why IPV6_DEFAULT is
disabled by default, and is only enabled if GlusterFS is configured with
`--with-ipv6-default`.
This has been the case since it was introduced in
I was meaning to propose removal of myself from the maintainers list for
some time. Never got around to it. So this is okay with me. A couple of
things.
1. I'm still listed as maintainer of glusterd2.
2. I still have admin access in Gerrit and Github org. I'd like to have
that removed too.
I've
97 matches
Mail list logo