git describe in master: 0.82.3-339-g60217f2 in game: 0.82+.4.0
Could need some consistency.
0.82-branch: In 0.81 (80, 79?) you could always directly compile the latest commit in that branch. Why is there a "post release version bump" after every new release now?
source tagging
Moderator: Moderators
Re: source tagging
the problem is, that we should not have merged the release branch into master one. if we had not done this, master would now be like this:
0.82-555-gffffffff in game: 0.82+.0.0
this can not be fixed for 0.82 anymore, but we will try to stick to it for the next mayor release.
the post release version bump is the right thing to do it. look at what the commit does... (sorry, do not know what needs explaining there).
we plan to get rid of the SCM managed version (GameVersion.cpp) soon, to it will be different again then. eg, version will not be tracked by git tags and GameVersion.cpp, but only git tags, and in special cases other files containing git version info (for source tarballs eg).
0.82-555-gffffffff in game: 0.82+.0.0
this can not be fixed for 0.82 anymore, but we will try to stick to it for the next mayor release.
the post release version bump is the right thing to do it. look at what the commit does... (sorry, do not know what needs explaining there).
we plan to get rid of the SCM managed version (GameVersion.cpp) soon, to it will be different again then. eg, version will not be tracked by git tags and GameVersion.cpp, but only git tags, and in special cases other files containing git version info (for source tarballs eg).