How to make a Kst release:

- update from CVS
- run a regression test and make sure it completely passes
- update kst/kstversion.h to set the version number
- set the version numbers in kst.lsm and kst.spec.in
- tag CVS
- make sure documentation has correct version for the <releaseinfo> tag
  of index.docbook and correct version of KST, QT, and KDE in the installation
  instructions of install-chapter.docbook
- update ../doc
- prepare for a KDE 3.1 install!  Set min config appropriately
- make sure configure has been run so that the spec file is created (with the
  appropriate prefix, otherwise it must be editted after)
- cvs2dist /path/to/kdeextragear-2 kst -n kst -v <version_number> -d
- unpack, remove any files that shouldn't be there, make sure docs and i18n
  are packaged properly, and edit any paths necessary (ex: spec file)
- generate the srpm: rpm -ts kst-version.tar.gz
- generate rpms as needed: rpm -tb kst-version.tar.gz
                        or rpm --rebuild kst-version.rpm
     - SuSE and RedHat style are typically generated.

- TEST

- update www/areas/extragear/inc/appinfo.inc
- upload packages and lsm to upload.kde.org
- mail ftpadmin@kde.org to notify them
- update omega.astro

- update kst/kstversion.h, kst.lsm, kst.spec.in to the next release 0.xx-devel

