https://bugs.kde.org/show_bug.cgi?id=389864
--- Comment #10 from RJVB <[email protected]> --- Or consider following KDevelop's approach: - current release version is 5.2.1; `git describe` returns v5.2.1-45-gbda9fd5a29 in the 5.2 release branch - the version used in the master branch is 5.2.40, for which there is no tag. However, `git describe` returns v5.2.1-368-gb4934d31d4 in the master branch. This is perfectly usable too as it clearly shows that the master branch is well ahead of the release branch. It is even preferable because it allows to continue merging commits between the master and release branches AND to have 5.2.2, 5.2.3, ... commits before moving on to 5.3.0 . I cited Okular earlier on, where `git describe` does return a sensical value in the master branch that relates it correctly to the release version. The project itself uses a completely different versioning which is weird but unlikely to lead to ambiguity since it is so clearly independent from the collective versioning. -- You are receiving this mail because: You are watching all bug changes.
