Posted October 19, 2016

its been in "alpha" for 2 years now
let me follow that up with that i dont like galaxy very much
Regardless those release management terms are somewhat arbitrary. More importantly, it's the software's ongoing developmental status that I think concerns people more than release management labelling terminology used. It seems clear they released it somewhat before it was ready in order to capitalize on the massive press of the Witcher 3 release, and ride the wave. From a business standpoint I can't fault them for that at all no matter how ugly it may have been under the hood, opportunities like that don't fall out of trees often and CDPR's next major game isn't slated for a couple more years at least likely. So perhaps they released early and they get some verbal black eyes for it over time, but ultimately it was worth it no matter how bad one's views are about Galaxy.
What's missing now is whether or not they have a concrete written in stone and non-growing list of features they're targeting for the official non-beta stable release, and what timeline they might be targeting for that. I'm not asking nor expecting them to publicly disclose that, but just curious that they actually have that internally at least. My biggest fear is that it stays in a semi-perpetual beta state and moves forward with creeping featuritis for years more to come. I'd rather see a very short small list of solid must-have features banged out and stabilized to release quality, then jam the version X.Y stamp on it and shove it out the door, maintaining a stable branch of bug fixes and minor incremental features off of that, while developing a next-gen version with larger features for down the line.
They've kind of hinted that they're already sort of doing some of that in public posts in the past. Someone from GOG mentioned a future 1.2 release would have more features although I'm not sure if they said what they would be for example.
Another question is - what the criterion are for measuring code quality and state of project to declare "out of beta, release quality" to aim for. It's hard for us to measure here on the outside, because we only really see the client front-end UI, but probably 90% of the code they are hammering on is backend services that are mostly invisible to the end customer, the APIs to talk to that, the stuff under the hood on the client side including the Galaxy library, etc. The client and it's web UI are a small fraction of all of that, but the only thing most of us really see, and if the UI doesn't change materially much over time - it gives the visual impression that nothing is happening even if a lot is happening behind the scenes that is just not anywhere near as visible.
Even acknowledging all of that though, it'd sure be awesome to see more UI visible changes happening that have direct in your face end user interaction and impact, with which users can measure visible improvements from release to release beyond just bug fixing.
Personally, I'm going to speculate that we'll see a Galaxy 1.2 before the end of the year however I think it will most likely still be considered a beta for some time to come. Hopefully they add enough major new features to draw more people's interest and to address other issues that put people off from it now to make them reconsider it in the future. Ultimately it's up to them to convince people to use it on the software's own merits though, but that has been their stated intention all along. Time will tell...