Difference between revisions of "Releasing Luanti"
Jump to navigation
Jump to search
(→The process: mention util/bump_version.sh) |
|||
| Line 11: | Line 11: | ||
=== Update version in source === | === Update version in source === | ||
| − | * '''Define''' a new version number in CMakeLists.txt | + | * '''Define''' a new version number by running util/bump_version.sh. Verify that this script correctly |
| − | * | + | ** updates the version number in CMakeLists.txt and the titles of doc/lua-api.txt and doc/menu_lua_api.txt |
| − | * | + | ** comments out the line in CMakeLists.txt that sets VERSION_PATCH to ${VERSION_PATCH}-dev |
| − | + | ** increments ANDROID_VERSION_CODE in build/android/Makefile | |
| + | ** and commits. | ||
* '''Tag''' the version in local git to allow the cmake versioning script to remove the git hash from the version. Do not push the tag to GitHub yet. | * '''Tag''' the version in local git to allow the cmake versioning script to remove the git hash from the version. Do not push the tag to GitHub yet. | ||
* '''Build''', get newest minetest_game, run and check if the thing seems to be working. | * '''Build''', get newest minetest_game, run and check if the thing seems to be working. | ||
Revision as of 22:39, 29 December 2014
Before releasing
Usually, a feature freeze for one week is announced in #minetest-dev. New features aren't accepted in this time and people focus on finding and fixing bugs.
The feature freeze and release date is set by core developers.
The process
This is mostly done by several core developers.
Update version in source
- Define a new version number by running util/bump_version.sh. Verify that this script correctly
- updates the version number in CMakeLists.txt and the titles of doc/lua-api.txt and doc/menu_lua_api.txt
- comments out the line in CMakeLists.txt that sets VERSION_PATCH to ${VERSION_PATCH}-dev
- increments ANDROID_VERSION_CODE in build/android/Makefile
- and commits.
- Tag the version in local git to allow the cmake versioning script to remove the git hash from the version. Do not push the tag to GitHub yet.
- Build, get newest minetest_game, run and check if the thing seems to be working.
Build Windows version
- Visual Studio 2010 currently makes best results (?).
- Currently built by BlockMen (0.4.10). They have sound, gettext, cURL and TTF support.
- Since 0.4.8, a MinGW build is also included, built by sfan5.
Be sure that the Windows build works before continuing to do anything!
Tweak Windows package a bit
- Include minetest_game or other subgames that were decided on before the release.
- Include msvcr100.dll and wrap_oal.dll in the package (bin/). The latter is one of the OpenAL DLLs that the CMake install scripts are currently missing. Those making official builds probably already know what they are doing.
Upload Windows package to somewhere
- Windows packages are hosted at GitHub: https://github.com/minetest/minetest/releases.
Update branches and tags of minetest and minetest_game on GitHub
- See previous tags. Use the same tag for all of them; eg. "0.4.4".
- GitHub's release functionality can be used if preferred.
- The new release should be merged to the stable-0.4 branch on both minetest and minetest_game.
Update links on minetest.net
Some people from the community can edit the minetest.net page (celeron55, PilzAdam, rubenwardy, BlockMen, Jordach, sfan5).
Write a release notice
Usually a new topic in the News section of the forum. Changelog can be found here.
Update stuff on launchpad to get Ubuntu builds for the new version
Juhani Numminen hasn't been around in a long while, so celeron55 or PilzAdam must update Launchpad.
Notify other known package maintainers
- emptty (@ chat.freenode.net) maintains Debian packages.
- Zeitgeist_/damiel (@ chat.freenode.net) is the proxy-maintainer for Minetest in Gentoo.
After releasing
Reenable -dev version suffix
- Uncomment the line near CMakeLists.txt:22 that sets VERSION_PATCH to ${VERSION_PATCH}-dev.
- Commit.