On Fri, Jun 1, 2018 at 9:41 PM, Isaac Chou <Isaac.Chou@xxxxxxxxxxxxxx> wrote: > Hello, I need help on this topic again. I need to inform our customers what release this issue will be addressed in. I checked the 2.17.1 binary release recently and found that the fix is not included. Can someone help me with that information or point me to a document that I can use to determine it myself? It's in 2.18.0-rc0, so it should be in the next 2.18.0 release (unless something horrible happens but very unlikely). -- Duy
