I'm trying to figure out the best way for me and my team to use the releases feature to manage our work.
We all want to be able to make changes independently of one another, and release those changes to live when ready.
Currently the releases feature doesn't seem to be able to support this and seems more like a 'save state' at a certain point in time.
Unless i'm missing something, there is no way currently for person A to make a set of changes they need to make and for person B to do the same, and then for them to each release their changes independently when ready.
This is a typical feature branch style workflow we're all used to and it would be great if Retool supported this.
I have noticed there is a 'Source Control' feature on an Enterprise plan, but we are not an enterprise. Any team that works on building systems of any kind needs source control no matter the size.
Any help/suggested workflows are much appreciated!
This kind of feedback is super understandable and something we hear fairly often. In its current form, creating and publishing a new release will push all staged changes to the live version of the app. This works great for development sprints or cycles, for example, but isn't as useful for continued asynchronous development by multiple individuals.
It's definitely not perfect, but the solution that I have recommended in the past is to utilize modules as a type of rudimentary branching system. An individual developer can work on a granular portion of the overall app in relative isolation, releasing and publishing new versions of that code on their own timeline. This does result in your app development being extremely compartmentalized, but it comes with some of the advantages of gitflow.
I hope that helps! I'll add your feedback to some of the internal conversations we have on the topic of feature parity and pricing.
