Closed
Description
It's been mentioned in the original blog post's comments section, and on this thread: the current way releases are finished merge the release branch into master and develop, but does not record a relation between them, which makes git-describe
output very inconvenient (if not to say very confusing :)).
For example: consider the case where you have a version 1.0 tagged, then finish a new 1.1 release. When using git-describe
, it scans the commit tree upwards, and finds 1.0 as the first tagged commit, generating a misleading identifier somewhat like 1.0-52-g25def71
, instead of something like 1.1-8-25def71
.
This requires a change to the original branching model, too.