version naming problem

once upon a time.... we had only one master branch.... the naming was automated, looked for the latest tag, computed the distance, and assembled something like this: v1.2-beta-BlackForest-681-gfb545b33

NOW, we have a master and a developer branch..... tags are no longer done in the developer branch.... but in the master branch. Consequently, I obtain v1.2-beta-BlackForest-681-gfb545b33 despite the developer branch being base on v1.3.2-beta-Mijas....

I understand that having the same tag in two different branches does not make sense and, most likely, is not even possible.

So here my suggestion: should we use v.1.3.2-Mijas.... for the master and v.1.3.2-beta-Mijas... for the corresponding versions in the two different branches?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information