Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 334
    • Issues 334
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2226

Closed
Open
Created May 22, 2018 by Sven-Bodo Scholz@sbsOwner

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
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking