From The Mana World
Revision as of 13:17, 25 February 2009 by Jaxad0127 (talk | contribs) (→‎Notifying the package maintainers and websites: link to Arch Linux package details instead of listing Bjorn as maintainer (he isn't anymore))

Updating the version and release date

The program version and release date are mentioned in several places. Some other places are also important to check before making a release.

  • CMakeLists.txt – version
  • configure.ac – version
  • INSTALL – dependencies and their versions
  • NEWS – version, release date and changes
  • README – version and release date
  • data/help/changes.txt – version, release date and changes
  • data/help/header.txt – version and release date
  • src/main.h – version
  • src/winver.h – version

Making a clean tarball

Authors and packagers should work on making a clean tarball, which has no .git folders, no Makefiles, no .deps folders, etc... That kind of clean is needed when uploading sources such as for debian, and can be obtained thanks to make dist, with automake.

To test that the distribution compiles and installs with just the files included in the release, make distcheck can be used. However, you should also make sure that it actually runs.

Creating a windows installer

  1. Clone the Git repository of the eAthena client. The directory where you have the cloned repository will now be referred to as "TMW"
  2. Get Nullsoft Scriptable Install System
  3. Get Code::Blocks and all libraries.
  4. Get Gettext for windows
  5. Get the music package and put it into the TMW/data directory (so you have TMW/data/music/*.ogg)
  6. Open TMW/tmw.cbp with Code::Blocks and compile the project
  7. Copy msgfmt.exe and all DLL files from the directory "bin" of your gettext installation to TMW/packaging/windows
  8. Run the visual basic script TMW/packaging/windows/make-translations.vbs to compile the gettext translation files
  9. Run the NSIS script TMW/packaging/windows/setup.nsi using NSIS

You will now have a distributable installer in TMW/packaging/windows/

Notifying the package maintainers and websites

Normally first the source and Windows releases are made. After verifying everything works with several people for at least a day, the release will be tagged in Git. At that point the release is official and the package maintainers should get started on producing their package.

The following people are responsible for updating their packages:

The following people are responsible for updating the respective websites:

Updating the wiki

The following pages may need to be brought up to date with the new release. Anyone may update these pages, and are encouraged to do so.