Not sure what might exist in the way of written documentation. There is
this:
https://musescore.org/en/developers-handbook/git-workflow
and it makes clear that the official way to develop for MuseScore is on
master; it doesn't even mention other branches. This is basically how it
been for as long as I've been developing (pre-2.0). I'm not really the
definitive authority here, but my understanding is this:
master - like the name suggests, this is where all future development is
focused. The assumption is that this will eventually become MuseScore 3
2.2 - it is possible but by no means definite that there will be additional
"point" releases before MuseScore 3. As bugs are fixed on the master
branch, if the bug also applies to 2.1 and is deemed worth fixing for a
point release, those commits can be cherry picked and applied to this
branch. Occasionally master and 2.2 have diverged too much for this to
work automatically, and in those cases, it might be necessary to manually
rebase your fix to work on the 2.2 branch.
2.1, 2.0.3, 2.0.2, etc - these are basically snapshots of what has already
been released
It's possible some small detail of this is off, but not the general point:
all new development should be on *master*. If it is then determined that a
change is worth applying to 2.2 as well and it can't be automatically
cherry picked, only then would there be reason to need to thin developing
against 2.2.
On Sun, Aug 20, 2017 at 1:48 PM Ralf Mattes <[email protected]> wrote:
>
> Am Sonntag, 20. August 2017 21:21 CEST, Marc Sabatella <
> [email protected]> schrieb:
>
> > Could be, or it might just be that while 5.4 is recommended and what
> > released builds use, 5.3 might technically be sufficient.
> >
> > Still, the more important question is the one I asked - is there a reason
> > you are building 2.2 at all?
>
> I guess because of Thomaso was told by Joachim:
>
> > Hi Thomaso
> >
> > Trying to build 2.0.2??? What not the latest official release 2.1, or
> even
> > 2.2?
> >
>
> > Normally, people should *not* be doing that,
> > especially for development purposes. All new development should be on
> > master.
>
> Is there any documentation on the semantics of the different branches?
>
> Cheers, RalfD
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
