I know what you mean. But cut the man some slack. There's some things you could blame the community management for. (E.g. sometimes several months between them even doing one statement, which can make you wonder, what they are doing at all. ) But the current situation is not on them to blame.
Right now, the community team is merely the ones taking the heat from us. They are not responsible for the mess we all are in, yet they have to stand in front, while those who made the decissions sit in the back. Where we still don't know what's going on there, if they finally, after so many years, decided to actually take responsbilitiy and get things in order. Or if they now, after delivering a product below minimum viability, try to also get away with a minimum-viability plan of how to fix things.
They gave us a date when we'd get the plan: 4th of June. Two days to go. Then we take a look at it and, if it's not really, really great, give them all the heat they deserve for that. But we should really try to direct it to those who are responsible, not the small community manager or even the regular coder, who both are just tin soldiers, doing what they were told, without having any influence on release dates and bugfix cycles.
So, save your ammo for the 4th of July...