Reputation: 4747
I am using git along the lines of this model. I am about ready to do my first release. I don't work as part of a team, there's just me. Is there any necessity to use a 'releases' branch? I have a feeling it might be just complicating things and so I was going to just merge changes from the development branch directly into the master instead, and proceed with future releases in that way.
Upvotes: 0
Views: 49
Reputation: 11791
It is't needed, but if you want to ship version 1.0, while working towards 2.0 you'll want not to abandon the 1.x series, and cherry pick changes or apply local bugfixes. Having a release branch and development branch(es) is useful in that case.
Upvotes: 0
Reputation: 185691
There's no need to create a release branch unless you want to start doing work on your develop branch that doesn't belong in the upcoming release.
Upvotes: 2