Hi! We name release branches and tags specifically, but you can name your own branches whatever you like :). It's nice if they have a descriptive name like "fix-foo-bug".
For 2.3.0, there is no release branch yet so you would branch from master. For 2.2.0, branch from the "2.2" branch since it has already been cut from master. On Sat, Sep 22, 2018, 4:12 AM <javier.vilarr...@gmail.com> wrote: > Hi. > > Just a fast question. > > Any etiquette rule on how to name GIT branches? > > And from where to branch? I mean, the bug I want to work on has been > assigned to milestone 2.3.0. Do I branch from master or do I branch > from somewhere else? > > Thanks in advance :) > > Javi > > > > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel >
_______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
