If you go look at the release notes for Beta36, this bug number is not included in them, so one can conclude that this bug is still open. Since L&L no longer provides timelines and estimates, that’s the most information we’re likely to get until it’s actually fixed.