No. The issue in the article is fixed in 1.0.1 and the fix is not a stop gap. Here's [0] the pull request. And here is the correct github issue[1]. You are linking to a completely unrelated issue.
The article is referring to a bug where mining of zaddr transactions were delayed under some circumstances. They were still mined. The post we had announcing the bug was rather terse and so some details were lost. The article was written from that post. We(Zcash) were the ones who found the bug and announced it.
As you can see from this transaction[2] before the update, there were zaddr transactions that got mined.
It does of course make an amusing headline to say private crypt currency has bug that prevents private transactions and it was written off of scant information, so it's understandable. But all that happened was private transactions took longer under some circumstances and that has now been fixed.
The article is referring to a bug where mining of zaddr transactions were delayed under some circumstances. They were still mined. The post we had announcing the bug was rather terse and so some details were lost. The article was written from that post. We(Zcash) were the ones who found the bug and announced it.
As you can see from this transaction[2] before the update, there were zaddr transactions that got mined.
It does of course make an amusing headline to say private crypt currency has bug that prevents private transactions and it was written off of scant information, so it's understandable. But all that happened was private transactions took longer under some circumstances and that has now been fixed.
[0] https://github.com/zcash/zcash/pull/1718 and here is the correct issue [1] https://github.com/zcash/zcash/issues/1705 [2] https://explorer.zcha.in/transactions/de1d78ee310ba2c9fbeb13... pre update, there were zaddr transactions.