graceful cairn
I'm legitimately curious, if a developer could provide some insight/transparency into the update workflow you guys use, that would be super cool. I'm just wondering what sort of phases/stages changes go through before it gets pushed as an update. For example, idea -> approval -> development -> code review -> playtesting -> push, or something similar. I'm interested in what it looks like from the time we see things in the dev diary to when we actually receive it. On another note, if a "public test" branch that received more experimental builds was made to help playtest bleeding edge stuff, I'd probably be interested. As a software engineer myself, I get excited by changelogs and like trying out every new detail haha
gloomy flame