Posts: 681
Threads: 26
Joined: May 2014
Thanks: 0
Given 8 thank(s) in 37 post(s)
We should really give MCServer a version number with OpenSource style like 0.4.13 or something. The Number in fact doesn't matter, but then we do have something to ship with the querys from the query protocol. I know that we could also use the git revision code, but this kind of versioning is not that readable. And we could higher the version number with each bigger step we take into compatibility with vanilla.
Posts: 4,621
Threads: 113
Joined: Dec 2011
Thanks: 51
Given 58 thank(s) in 410 post(s)
Maybe it's possible to add the buildattempt to the download name. For example "MCServer build #451.tar"
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 0
Given 4 thank(s) in 61 post(s)
The problem is that we cannot calculate the version numbers from git. Unless you want a horrible script that only works when the git command line tools are installed. So we would need to implement a versioning cycle. Then we have to decide when we bump the version? If its every commit we get different versions. If its every merge it makes PR's more work to merge because we cant use the github ui. If its periodically it will hardly ever happen. If its on a major change what counts as a major change?
It would be far more useful at the current stage of development to return the commit id.
Posts: 274
Threads: 48
Joined: Mar 2015
Thanks: 0
Given 0 thank(s) in 10 post(s)
But I agree, a version number would help a lot. Users like me are looking for that and we're like "Heh... what ... which one?"
Posts: 4,621
Threads: 113
Joined: Dec 2011
Thanks: 51
Given 58 thank(s) in 410 post(s)
03-29-2015, 05:09 AM
(This post was last modified: 03-29-2015, 05:09 AM by NiLSPACE.)
Or to log it in the console when the server starts?
Posts: 6,486
Threads: 176
Joined: Jan 2012
Thanks: 40
Given 157 thank(s) in 838 post(s)
I believe it's already logged into the console, but API is much better.
Posts: 1,162
Threads: 68
Joined: Mar 2013
Thanks: 0
Given 10 thank(s) in 100 post(s)
Why dont we just do releases in github named MCServer 0.X.X and set todos for next releases and increase version number when getting closer to vanilla. Those releases would be marked as stable and avaliable in github releases tab for all OS
Posts: 681
Threads: 26
Joined: May 2014
Thanks: 0
Given 8 thank(s) in 37 post(s)
Yeah and the build-server would only need to compile the things in the release stage