As seen in the comments of that post, it is a game breaking issue for many people. It would be very much appreciated if it could be included in an earlier update rather than waiting until 2019.3 is released.
They state the version where they fixed it (the current code base) and usually they merge the fix back into previous maintained code bases (versions) when it appropriate and doable. So probably you will see the fix in previous versions as well, keep an eye on the change logs they are putting out.
So we’re now up to 2019.1.6 and this is still not fixed. The solution is spelled out in the issue tracker so it’s not like it is not known how to fix it. I would really like to know why this fix hasn’t been included yet and still shows that it is fixed in 2019.3, which is probably still quite a while before a stable version of it is available. I’m not the only one wondering, check the issue tracker
Honestly, more than a month to fix what is clearly a show-stopper bug. I get why all the engineering resources are on 2018.3, but it really feels like someone dropped the ball here.