I'm not sure I agree. I can tell you as part of a development team, that temporary patch up jobs should be avoided at all costs, because you often never get given the opportunity to go back and fix things up properly and the patch job becomes permanent - as does any flow on issues. You're left with inefficient code, and that might inadvertently contribute to problems for other people who might have a hard time untangling your patch up.
I think that because this is such a widely reported issue, that is taking an extended period of time to fix, it is reasonable of us to inquire as to what the status is. But I'd prefer to wait so that it is solved properly, rather than in a way that is likely to lead to other issues down the track