Well, nobody says anything against that, but TeamSpeak still makes a big TramTram when too much is said again. It also takes the fun out of it for beta users if you already know what’s coming in the new update, but you can’t test it yet.
Well then you might as well forget about any new feature. Of course you can’t make an untested new feature available to everyone right away, but if it drags on for months, maybe you should prioritise something else for the next update. On another note, if you use the “debug mode”, which you shouldn’t use in the beta because it might break your client, I wonder why there’s even the option to use it to break everything. It makes no sense.
In addition, you also first need the requirements to set a homebase, which currently no one but TeamSpeak partners & alpha testers would have anyway.
The fact is, the way the client is at the moment, you have the possibility to scrap the client without the homebase. But the fact that even closed beta testers have nothing new in the client for over 3 months is simply a weak performance, regardless of whether there are only a few developers or features have not yet been sufficiently tested. Then you should just as mentioned above, first put the focus so that you do not stop the whole beta phase because of a feature or is that because of anything else?