On 08/23/2018 07:18 PM, wkmail wrote:> Weren't we supposed to get a new 4.1.x? this month on the 20th?
<grin>
Yes, most of the tagging preparation is done, it was staggered
considering 3.12 release delays (Note to self: should let the lists know)
>
> In particular I am interested in the client Memory leak fix as I have an
> VM cluster I need to put into production and don't want to immediately
> turn around and do the upgrade.
> Any word on that?
The leak in 3.12 was identified to the patches in this [1] bug, and
these patches are already part of 4.1 since 4.1.0. So, unless there is a
newer leak in 4.1 there are no fixes in the queue to address the same.
Could you provide more context on this, like mail threads or bugs that
you are looking for?
[1] Bug fixed recently in 3.12, but already in 4.1.0:
https://bugzilla.redhat.com/show_bug.cgi?id=1550078