Do not bump project's version constantly about open-realms-of-stars

[tuomount]

Let's go with ?.?.?-SNAPSHOT and one version bump per release cycle. I am also okay removing the Beta version suffix.

[tuomount]

Update 0.25.0 into changelog. Change log is now just empty for 0.26.0. I was thinking to add that title there when we actually have something for change log, but there is always a chance it forgets from there, like 0.24.0Beta was forgotten from the change log. Closing this one.

[tuomount]

Idea was that only stable versions have published releases. I think that those version between stable ones should be distinct somehow. How git commit identifier could be get into version number? I would guess it would require some plug-in to maven. For example 0.24.21Beta-c6705cbf would be excellent. I admit that I have been quite lazy with Maven, and I even found it is easier to manually pump up third number in version everyday when I make changes, than looking for maven plug-in for it. 😄

Another thing I would like to have is that there would another command like mvn verify, but it would not run full game JUnits since those can take quite a time depending on your CPU. But those are good when making AI changes or something else big game feature changes.

[BottledByte]

For example 0.24.21Beta-c6705cbf would be excellent

I can offer you to have ?.?.?-SNAPSHOT version label format for local developer builds and ?.?.? for official GitHub Releases, where you have to do only 1 commit with version bump per release cycle, each time after you do a GitHub Release. You would just have to run release build with different command (since you do Releases by hand). This includes propagation of this information to the Game itself.

I can also make it that there is no version bump commit per release cycle and developer builds will be marked with Git commit SHA. No modifying version strings ever again. But will have to get me access to CI for that 😉

So, no more "daily version bump" commits?
And will you let me remove that Beta version suffix while at it? IMHO, it looks bad. 😄
You accept? 😉

[BottledByte]

@tuomount After release, it is necessary to update src/resources/resource/changelog.txt also with heading that has the version string of the last released version.

Without this, the changelog in game will look like this for developer builds, not mentioning the last released version:

Otherwise, I can confirm that in released version 0.25.0 the changelog looks OK. 👍

And congratulations to the release of 0.25.0. 🎉
... I will start sending more PRs. 😄