Well he was sarcastic, but it was a pretty bitter joke.Maybe I'm wrong (a translated text isn't always perceived as the author intended), but I think it's just a phrase of sarcastic humor. Nothing bad.
That said, BD isn't known for stick his long-term objectives . The problem is not the time between updates, but the significant difference between the advertised target and reality. (e.g.: If he says the update is in 2 weeks, I don't want to wait 3 months. If he says the update is in 3 months, no problemo, I'll wait 3 months.)
I love this game and that's why I've supported the dev for so long. But as I said on Patreon, BD needs to set goals that are achievable over the long term. While working at his own pace, he has to decide what his next update will contain, how long it will take him, how much time he will lose in case of unforeseen events, etc. Then, he adds a safety margin before announcing a release date. Since the update won't be delayed, nobody will be angry about this. If he does more work than the scheduled update, he saves it for the next one.
I agree that he's bad at estimating how long updates will take. I mean, word on the grapevine is he said the update would drop before the end of the month but it obviously hasn't. But it's not an easy thing to estimate. Any software engineer will tell you that projects or updates go over their time budget all the time. The main issue in WVM's case is that he prefers tangible updates (I.e. stories actually progressing), which means long updates which means a big potential variation in how long it will take.
There was this leaked doc that showed he had been testing for over 10 days now. He could've released with all the bugs and mistakes 10 days ago. But then the quality would be lower. It's a trade-off he has to make about what he wants to actually put out there.
Personally I've had 5 years to get used to him getting the timetable wrong and it's something I've accepted. I wouldn't be here checking for updates if I hadn't.