"Developers may release either a closed beta also called private beta, or an open beta also called public beta; closed beta versions are released to a restricted group of individuals for a user test by invitation, while open beta testers are from a larger group, or anyone interested. Private beta could be suitable for the software that is capable to deliver value, but is not ready to be used by everyone either due to scaling issues, lack of documentation or still missing vital features. The testers report any bugs that they find, and sometimes suggest additional features they think should be available in the final version."

https://en.wikipedia.org/wiki/Software_release_life_cycle#Open_and_closed_beta

This is not a even closed beta.

The number of user allowed into is quite high, the comms with devs quite reduced, if at all.
The SW is not missing some vital features, is barely functional.

Moving the goal posts, are we?

Why should that be the case ? There is a growing number of users that surely passed the three digit amount a while ago, but miraculously the board isn't flooded with comments agreeing to your assesment.

Having myself a background in software development for 10+ years, I would say for a beta release its quite stable and functional - of course there are still a lot of features missing, but that was always clear from the getgo.

Maybe you should think about your definition ?

But then he wouldn't be able to complain so much.

Also, why do people have the feeling devs own constant communication in beta phases? They ARE getting feedback, one way or another (even from people who doesn't post anything, which I imagine it's the majority.) The devs... I much rather they work by themselves. Also prefer GOG doesn't spend valuable PR people here, come one.

Should not spend valuable PR to do this?
This is what they should do. Engage the community.

Especially on some new, exciting, shiny piece of software, just after they called for an... public closed Beta (?).

Ok, but I actually don't care. :D

Well, we'll have to agree to disagree then. Cheers

Uh ? And what about this "Closed beta" ?

It has improved quite a lot since it initially launched and almost all the issues I had with it were resolved. The only things I'm missing are the absence of a dedicated profile page, ability to see goodies and game's version (all of which were present in G1) and proper outside store integrations instead or users made.

There's a few bugs here and there, like game still showing when uninstalled but that's nothing a quick reboot of the app can't solve.

It's far from perfect and I agree that many features Galaxy 1 had were trully missing at first, but it's getting better and by the amount I'm using it, it's far more stable than some other very liked store app. I'm even surprised how quickly I got used to bookmarks which I thought, at first, were a stupid idea. I'm still not entirely on board, but it's not getting in the way of me playing daily, at all, so I'm fine with that.

It's true GoG isn't communicating too much with the users but why is that a surprise ? Since when are they actively communicating with users ? Meh.

Well as said before a beta meaning change from people to people. But if I remember well my project management course. The standard milestones before realease are the following: Alpha beta and release candidate. (English is not my first language so I'm translating the terms as I can. Hope I won't butcher the explanation too much)
Full disclaimer: I don't have my invite so I'm speaking theoritically here.

Generally you consider a minimum acceptable feature and the planned features on release.

The minimum acceptable features is basically a rough WIP that you can consider showing a client. It will have barebone features and is in a usable state despite a lot of bugs. Before that it's alpha, after that it's beta.

Here their minimum seems to be launching and managing gog games, support for community plugin integration and a few official plugin.

Then you have the release candidate, which contain all the the planned features on release but still need bug hunting before release (except for the features that get axed between the planning phase and the release.)

So yeah what should be in each milestone will vary from PM to PM but the definition as I was taught is the above

Considering those definitions, what mqstout is looking for is a release candidate not a beta

for me the showstopper is the/my missing tags. hope this will be included in the final release which i'm looking forward to.