DEV Community

loading...

Discussion on: How to use git efficiently

Collapse
t0nyba11 profile image
Tony B

Close to the approach I like, but missing aspects some projects need. If you need to have some sort of Freeze where only fixes to a release are made, but you don't want everyone to stop using the shared branch, you need a branch for the Release Candidate itself. Then naming the branches Production, Release_XX, and Development makes it easier for most people to understand the processes. Makes patches to releases easier too - especially if different releases are in the wild.

Also, ask any 2 developers what Master branch is for, and you will get 3 answers. Best to use a different name. :)

Collapse
adityasridhar profile image
Aditya Sridhar Author

Agreed :D

That will make things more easier to follow