We are evaluating if we can push this change into 5.3. If we can do this, then it will be available for the next 5.3 patch release. Roughly speaking, we do 2-3 patch releases for a given release on a 4-6 month schedule. Latest release for 5.3 is 5.3.21 (which does not have this fix in it). For our next major release, I am sorry, but we cannot give out details at this point when it will be released.