Hi all, I don't think that we should adopt git flow in its entirety - it would be too complicated. However, i think that we can manage release branches like described in gitflow.
I think we should get back to this topic when it's time to think about new release. Best Janek W dniu poniedziałek, 27 kwietnia 2015 Carl Sorensen <[email protected]> napisał(a): > In another project that I am working on they use the gitflow branching > model. > > It seems to be quite robust in terms of > > a: Freezing features for release while at the same time providing a means > of working on new features. > > b: Providing formal methods for getting critical bug fixes into both the > released version and the development version. > > c: Clarifying whether bug fixes are part of regular development or > critical fixes for production. > > The flow is described here: > http://nvie.com/posts/a-successful-git-branching-model/ > > I wonder if we should adopt something like this for LilyPond development. > > Thanks, > > Carl > > > _______________________________________________ > lilypond-devel mailing list > [email protected] <javascript:;> > https://lists.gnu.org/mailman/listinfo/lilypond-devel > _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
