The problem is not in communication, it is in a lack of communication.
The first post on Sep-13 said the patch was done, but might not be released this week. The post then went on to make numerous fix promises and
The post was met with the excitement that it was designed to elicit. The problem with this was that it implied that the product would be soon forthcoming.
For the next 16 days there was more information, and the joy led to the natural feeling of disappointment and deception.
The posts that came were patronizing. "Actually, this is not a deadline, nor was there ever a deadline. We will release the patch when we are ready to do so.
We are happy to give you time estimates based on the current situation, but situations change. We can keep totally silent, if you prefer."
But you can't raise people's hopes with a list of fixes and take that tone with them when you don't deliver. One comes off as childish and irresponsible when one posts such things, and then follows up today with, "I posted here as a thank you for all your feedback, but it is not my job to keep you informed." - to make the posters who feel justifiably deceived seem ungrateful.
You could have solved the whole problem by posting on say... Sep-20 that there had been a problem with the patch, and that it would be indefinately delayed, and then thanking people for their patience.
But you didn't do that Alex, and you look really bad as a result. Stick to programming and away from PR.
If you make a promise - keep it, or explain why you can't. Don't belittle people for expecting you to deliver what you promised.