[Gluster-users] Gluster release 3.12.13 (Long Term Maintenance) Canceled for 10th of August, 2018

Discussion:

Jiffin Tony Thottan

2018-08-14 10:42:28 UTC

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 delay to inform above details.

[1]
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055160.html

Regards,

Jiffin

l***@ulrar.net

2018-08-14 10:50:06 UTC

Permalink

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 OOM killer ..

Post by Jiffin Tony Thottan
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 delay to inform above details.
[1]
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055160.html
Regards,
Jiffin
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

--
PGP Fingerprint : 0x624E42C734DAC346

Ravishankar N

2018-08-14 11:00:38 UTC

Permalink

+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/

Post by l***@ulrar.net
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 OOM killer ..

Nithya Balachandran

2018-08-14 12:18:30 UTC

Permalink

I agree as well. This is a bug that is impacting users.

+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/

Post by Jiffin Tony Thottan
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 delay to inform above details.
[1]
https://lists.gluster.org/pipermail/gluster-devel/2018-Augus
t/055160.html
Regards,
Jiffin
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

Hari Gowtham

2018-08-14 12:59:05 UTC

Permalink

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.

Post by Nithya Balachandran
I agree as well. This is a bug that is impacting users.

+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/

_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users

--
Regards,
Hari Gowtham.

Jiffin Tony Thottan

2018-08-16 03:17:05 UTC

Permalink

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

Post by Nithya Balachandran
I agree as well. This is a bug that is impacting users.
+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/
<https://review.gluster.org/#/c/glusterfs/+/20723/>
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 OOM killer ..
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 delay to inform above details.
[1]
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055160.html
<https://lists.gluster.org/pipermail/gluster-devel/2018-August/055160.html>
Regards,
Jiffin
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users
<https://lists.gluster.org/mailman/listinfo/gluster-users>
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users
<https://lists.gluster.org/mailman/listinfo/gluster-users>