elcook: First things first, let me tell you that
we do have a devportal open to all our partners, not only for those who are implementing Galaxy features. Within this portal every developer can get a hold of our build delivery tool that works exactly like steampipe -
updating a game on GOG is a matter of executing a single script.
Well that interesting and not the info I've been hearing which made it seem like the tools GOG offers wasn't as advanced when compared to Steam. Very cool.
elcook: Just to be on the same side, not every partner has switched to this system, but the ones who did are in the grand majority, and we are strongly encouraging all partners to use it.
Apart from the tools, documentation and dedicated Product Manager, each partner has an entire dedicated support team at their disposal.
Also interesting.
elcook: What's more, after the build gets published on GOG via devportal, we test every single one of it - the reason for that is that we want to able to provide our developers with feedback regarding their games to maintain the quality of our products.
Even update builds or just new builds to GOG? The latter is fine but the former isn't because this slows down updates. We have a rollback feature for this reason.
Or do you allow the updates to show on Galaxy immediately, but still test them after?
Could you clarify this?
elcook: Hope this will one and for all clear things up regarding the build delivery system on GOG. Just remember, how the developer provides builds to GOG depends on many factors, however the final decision is always up to them.
Yes but we would love for this to be more open. You guys should make your SDK public and document your API publically on a wiki or something like Steam does.