I agree as well. This is a bug that is impacting users. On 14 August 2018 at 16:30, Ravishankar N <[email protected]> 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 side. This needs to go in too. > Regards, > Ravi > > [1] https://review.gluster.org/#/c/glusterfs/+/20723/ > > > On 08/14/2018 04:20 PM, [email protected] wrote: > >> 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 .. >> >> On Tue, Aug 14, 2018 at 04:12:28PM +0530, Jiffin Tony Thottan wrote: >> >>> 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 >>> [email protected] >>> https://lists.gluster.org/mailman/listinfo/gluster-users >>> >> > _______________________________________________ > Gluster-users mailing list > [email protected] > https://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-users
