Francesco Pizzolante writes: > I understand, but I find it weird that a same version number (like > 8.2.4) gives different functionalities/fixes/patches according to the > git branch you take the sources from.
You don't understand what the version numbers mean. > Shouldn't the maintenance branch keep the same version number until > a new release is made (i.e. until the master branch is fully merged into > the maint branch)? The maint branch contains the release (8.2.4 for your example) plus those patches that are purely bugfixes (i.e. do not alter, remove or introduce features). In your example, eight such patches had accumulated, placing you at commit f1b933: release_8.2.4-8-gf1b9339. The master branch includes everything on maint plus any patches that alter, remove or introduce features. That amounted to 350 commits past the 8.2.4 release at the merge into master (d55f06), including those eight from maint: release_8.2.4-350-gd55f063. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
