# $Id: Release.txt 4503 2007-02-27 16:43:46Z wjpalenstijn $


How to make a release
*********************

Preparing and testing CVS
=========================

* Make sure that version numbers in 
    configure.in
    gemrb/includes/globals.h 
  are correct for the upcoming version.

* Update NEWS with highlights since the last release 

* Update ChangeLog with entry about release

* Make sure that GemRB CVS is in compilable and runnable state

  - download a clean CVS tree and test it.

  - Make distribution .tar.gz  (make dist) and test it as well -
    especially make sure all needed files are included.

* Tag current CVS to version number e.g. GEMRB_0_2_3
  i.e. in the gemrb root directory do
    cvs tag GEMRB_0_2_3

* Update from CVS to the tagged version


Source release
==============

* on Unix/Linux: 
  ./autogen.sh
  make dist


Linux binary release
====================

  ./autogen.sh
  ./configure --prefix=/usr/local
  make
  make install DESTDIR=/tmp/fakeroot
  cd /tmp/fakeroot/usr/local
  copy ~/GemRB-binary.cfg over etc/GemRB.cfg, rename to etc/gemrb.cfg
  strip bin/gemrb lib/* lib/gemrb/*
  sudo chown -R 0:0 *
  sudo tar cvzf ../gemrb-0.2.5-linux_i386.tar.gz *


Windows binary release
======================

* FIXME: To be defined....


Release and Announcements
=========================

* Put the tarballs/binaries into Releases on SF
  Source pkg details:
    Release name: GemRB 0.2.5 Sources
    File name: gemrb-0.2.5.tar.gz
    Processor: platform-independent ; Type: Source .gz

  Binary pkg details: 
    Release name: GemRB 0.2.5 Linux/i386
    File name: gemrb-0.2.5-linux_i386.tar.gz
    Processor: i386 ; Type:

* Test the downloads from sourceforge.net

* Announce on homepage, SF, #GemRB in channel and title, Gibberlings3

* Possibly announce on Freshmeat/Happypenguin
