We’re bringing back Bleeding Edge builds. They’re somewhere between a nightly and beta build. We will update them frequently and expect them to break things frequently.
These builds will be posted on the forums (and linked to on the main website) for anyone who wants to try the new Gaea features as they’re in development.
You can provide early feedback as features develop to help us make it as close to what you want as possible.
We’ll start with Gaea 2.3BE1 this week, as we’re very close to wrapping up Macro functionality as well as some much-awaited new tools.
Please note, Bleeding Edge builds are NOT considered Production Ready and should NOT be used for any projects that are important. They may sometimes break your file. On the plus side, they are self-contained and meant to run side-by-side with your normal Gaea install without interfering with them.
Are there going to be different branches for separate features? Because otherwise if there’s just a separate combined beta branch, it would be nice if one could just subscribe to it and always get updates with new features as soon as they are introduced, same as with branches on Steam, for example.
I’d much rather prefer to subscribe to beta testing once and stay at it instead of having to download each build myself. Ideally, it would just have a different app version in a folder like Gaea 2 BE that would share the appdata folder with license information, but keep its own ways of processing projects.
We don’t separate BE builds by feature. They’re usually milestone based and contain several features at once.
But yes, you can keep each BE build completely isolated in its own folder. We’ll have more information on this soon.
As Ty mentioned, Betas (and often Bleeding Edge builds) will be short lived and frequently updated. Since we are not spending time with thorough QA on Bleeding Edge builds, we can provide them at even a nightly rate when needed. This happened a lot with Gaea 2’s initial beta and we expect the same with Gaea 3.
I see. My main concern/hope is that they can be automatically updated within the branch in the app itself. =)
So I open my BE build, see an update notification, press a button and receive a fresh version of BE right on spot.
Yeah, I get it, just expressing that hopefully with frequent releases doesn’t come frequent need of downloading a fresh build manually from the site. So that they get updated in similar fashion as the main branch.
