I don't think I mind the branch per-release. It seems to make sense to me if we're going to have well-defined and relatively infrequent release points.... the big complaints I've heard about the standard github flow is it doesn't work well with the continuous deployment paradigm.
Also, how is forgetting to merge a Jira into a release branch different from forgetting to merge a Jira into the master? ;-) On Sat, Jul 20, 2013 at 3:26 PM, Jordan Zimmerman < [email protected]> wrote: > Currently, we're using a Github-flow-like workflow: a branch for the > current release; a master branch; branches for each Jira. > > I've come to think that the current release branch is unnecessary and > confusing. For example, I keep forgetting if I've merged all needed Jira > branches into it. What do folks think about just using master for the > current release branch? > > Also, feel free to offer any other Git workflow comments/ideas. > > ==================== > Jordan Zimmerman
