Often when I encounter (startup) teams using this git-flow inspired strategy there definitely are things going on with master that shouldn't be. For example: Feature A is in staging ('develop'), but can't get into prod…
"Whatever you call your branching methodology, if they last too long that's when the fun stops." Doesn't git-flow explicitly keep a long lived branch around by design? The whole concept of having "develop" run in…
What sort of repository and deployment structure are you using right now in which it works fine? I think that will influence the outcome a lot. I just was working with a client that used something like git-flow, where…
Often when I encounter (startup) teams using this git-flow inspired strategy there definitely are things going on with master that shouldn't be. For example: Feature A is in staging ('develop'), but can't get into prod…
"Whatever you call your branching methodology, if they last too long that's when the fun stops." Doesn't git-flow explicitly keep a long lived branch around by design? The whole concept of having "develop" run in…
What sort of repository and deployment structure are you using right now in which it works fine? I think that will influence the outcome a lot. I just was working with a client that used something like git-flow, where…