I think milestone for this bug was moved by mistake, fix is already commited to dev branch, it will go into 5.1.
I think milestone for this bug was moved by mistake, fix is already commited to dev branch, it will go into 5.1.