The Git-flow branching strategies include a feature branch "level" that exists between the develop and master branches.

I understand the rationale for release branches in scenarios where we are developing traditional user-installed software products (i.e. software that is installed on a users own laptop, host, VM etc). In this scenario there could be multiple older releases running on peoples hosts throughout the world. The ability to send out a patch for a specific old release is very useful in this scenario.

However, in scenarios where we are developing a SaaS product, every customer will be using the same release of software at any and every point in time. There is only ever ONE release available for a SaaS product, by definition. In the SaaS scenario it seems that the release branch has become redundant.

As there is only ever ONE release available in a SaaS product, I have stopped using release branches managing releases directly via merges from develop branch to master branch without an intermediary release branch. Hot fixes are managed using the same branch strategy as feature development (i.e. branch from develop and merge to develop) and then deployed to PROD through an accelerated deployment pipeline.

I would like to know if anyone has experience developing SaaS products and with or without feature branches and if there was any down-side to NOT using feature branches.

All feedback appreciated.

The Git-flow branching strategies include a feature branch "level" that exists between the develop and master branches.

I understand the rationale for release branches in scenarios where we are developing traditional user-installed software products (i.e. software that is installed on a users own laptop, host, VM etc). In this scenario there could be multiple older releases running on peoples hosts throughout the world. The ability to send out a patch for a specific old release is very useful in this scenario.

However, in scenarios where we are developing a SaaS product, every customer will be using the same release of software at any and every point in time. There is only ever ONE release available for a SaaS product, by definition. In the SaaS scenario it seems that the release branch has become redundant.

As there is only ever ONE release available in a SaaS product, I have stopped using release branches managing releases directly via merges from develop branch to master branch without an intermediary release branch. Hot fixes are managed using the same branch strategy as feature development (i.e. branch from develop and merge to develop) and then deployed to PROD through an accelerated deployment pipeline.

I would like to know if anyone has experience developing SaaS products and with or without feature branches and if there was any down-side to NOT using feature branches.

All feedback appreciated.

• git-flow

1 Answer 1

Yo, this setup lookin' way too overcomplicated, fam. Keep it clean and smooth like this: