On Tue, 27 Feb 2018 12:19:38 -0800 (PST) Matt Wilkie <[email protected]> wrote:
> > Please hold commits into master for just a bit longer. > >> > > > > I have just deleted the 5.8-dev branch. The master branch is now > > open. > > > > Feel free to create branches as needed for your own projects. > > > > Would it be easier to invert the process, and have dedicated releases > branches and then master never needs to be frozen? That seems more > logical to me (but I'm not that branch savvy, probably missing > something). I think what you suggest is probably more common. master is sort of the "~finished work being tested" branch, and new features are developed in feature branches, which are merged into master when they're ready. Then when a release is desired, a release branch is made from master and then that's tested / packaged etc. Then after the release I suppose you merge the release branch back into master, although not much may have changed in that sense. But at the end of the day whatever works works, someone who wants to keep pushing their work to the main repo. can always use a feature branch while master's closed. I guess currently master is effectively being used as a release branch. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
