Hi, Adding my 2 cents. In the past, I have seen both the models. Keeping two branches: One for Develop and another for Releases. At the same time, I have also found tagging the releases to be sufficient.
IMHO, we can go for the model that needs less maintenance & operational effort for our project. +1 for Chris's approach thanks, Gautam On Wed, Aug 19, 2020 at 1:50 AM Ryan Skraba <[email protected]> wrote: > Hello, > > As an aside, there's some specific meanings for the develop branch and > release branches associated with the "git flow" methodology[1]. I > don't think we're proposing to adopt this specific way of working, but > it might look like it! > > In the proposed sense, "develop" matches perfectly, but "release" for > the latest release isn't very common. In my experience, tagging > releases has been sufficient. > > Regardless, as long as we're clear in the documentation for > contributors: +1 (non) > > Thanks! Ryan > > [1] https://datasift.github.io/gitflow/IntroducingGitFlow.html > > On Tue, Aug 18, 2020 at 11:54 PM Justin Mclean <[email protected]> > wrote: > > > > +1 >
