Why only releases from your default branch make use of the release version naming scheme?

[Ian Kent]

In our deployment projects we have setup a release naming scheme using variables: ${bamboo.lein.version}-${bamboo.buildNumber}

The ${bamboo.lein.release} variable is injected from version stored in leingen (clojure build tool) project.clj file in source repository.

This naming scheme works great from integration/master build plan.

However, when we deploy from a release plan branch the naming scheme is changed to <branchname>-<incremented number>. This is messing up our release version naming scheme.

Why only releases from your default branch make use of the release version naming scheme??

[Marcin Gardias]

Good question...

I guess our idea was that people will typically deploy from single branch and we wanted release sequence to be easy to grasp. Since there seem to be significant demand to change it, we will reconsider this decision. I can't promise you any specific release number/date atm. though.

Please vote here: https://jira.atlassian.com/browse/BAM-14422