Since the issue seems to critical and there is no longer lock is held on
Master branch, I will try to do a 3.12 release ASAP.
--
Jiffin
On Tuesday 14 August 2018 05:48 PM, Nithya Balachandran wrote:
I agree as well. This is a bug that is impacting users.
On 14 August 2018 at 16:30,
Hi,
The RCA for the memory leak had a mistake. It is yet to be identified.
The patch mentioned doesn't fix it.
Its on the protocol client. If some one can take a look at it, it would be nice.
On Tue, Aug 14, 2018 at 5:49 PM Nithya Balachandran wrote:
>
> I agree as well. This is a bug that is
I agree as well. This is a bug that is impacting users.
On 14 August 2018 at 16:30, Ravishankar N wrote:
> +1
>
> Considering that master is no longer locked, it would be nice if a release
> can be made sooner. Amar sent a missing back port [1] which also fixes a
> mem leak issue on the client
+1
Considering that master is no longer locked, it would be nice if a
release can be made sooner. Amar sent a missing back port [1] which
also fixes a mem leak issue on the client side. This needs to go in too.
Regards,
Ravi
[1] https://review.gluster.org/#/c/glusterfs/+/20723/
On
Hi,
That's actually pretty bad, we've all been waiting for the memory leak
patch for a while now, an extra month is a bit of a nightmare for us.
Is there no way to get 3.12.12 with that patch sooner, at least ? I'm
getting a bit tired of rebooting virtual machines by hand everyday to
avoid the
Hi,
Currently master branch is lock for fixing failures in the regression
test suite [1].
As a result we are not releasing the next minor update for the 3.12 branch,
which falls on the 10th of every month.
The next 3.12 update would be around the 10th of September, 2018.
Apologies for the
