mirror-games/glest-source
1
0
Fork 0
mirror of https://github.com/glest/glest-source.git synced 2025-02-23 03:02:34 +01:00
Code Issues Projects Releases Wiki Activity

updated readme file in relation to version number management

Browse Source
This commit is contained in:
filux 2015-02-01 23:41:09 +01:00
parent 5192c3f87f
commit 8596f70479
1 changed files with 8 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/README.release-management.txt
View File

@ -11,30 +11,15 @@ Source and Data Archives:
=========================
There are 3 archives that are built for a given release (starting with versions
after 3.6.0). In order to build a release you must have all files checked out
of svn for that specific release (example: trunk)
To set the current version for release, modify the file mk/linux/mg-version.sh
and change the two variables:
OLD_MG_VERSION=3.6.0.1
MG_VERSION=3.6.0.2
*Note: Please ensure the MG_VERSION variable matches the version set in the
MegaGlest binary, this can be checked by running: ./megaglest --version
It is possible to have the mg-version.sh script NOT match the binary in cases
where we are releasing binary compatible updates to the archives in which case
we typically use a forth digit in the version # (as seen above)
After setting the correct verions in mg-version.sh you should call:
./mg-version-synch.sh
This will update associated installers to use the correct version stamps
To set the actual binary to the desired version you must manually edit
glest_game/facilities/game_util.cpp
const string glestVersionString = "v3.8-dev";
after 3.6.0). In order to build a release you must have all git repositories
checked out for that specific release (example, tag: 3.11.0) or downloaded all
source archives/"tarballs" which in their name have same version, equal to tag.
To set the current version for release, modify the file source/version.txt
and change there available variables.
During build (on linux by script build-mg.sh) version number will be updated
automatically everywhere where it is needed.
Then you only have to commit changed files.
#1. The source archive:
This archive contains source code for binary compilation of the application and