It should have made it in the 4.1.2 release, but it was mis-prioritized, unfortunately. If a 4.1.3 release is required, it will be in that release. If not, it likely wouldn't be included until the 4.2 release, which would be in the April timeframe.
The code fix in the other thread is pretty straightforward, and hopefully shouldn't be too complex to do yourself.
Good luck,
Alex