= Release Checklist for Bitten =

== Prepare source for release ==

Verify:
 * Build docs with command: `./setup.py build_doc`
 * Run unittests on all major platforms

Make and commit changes:

 * Update version in `setup.py`
 * Drop `[egg_info]` section `setup.cfg`
 * Update `ChangeLog` with release information and changes - make changes in trunk and merge to stable branch
 * Before first major releases:
   * `svn copy trunk -> /branches/<major>.x`

== Tag release ==

 * svn copy /branches/<major>.x -> /tags/<major>.<minor><beta?>
 * Commit message should contain a link to `[milestone:<major><minor>]`.

== Adjust source trees ==

Make and commit changes:

 * Reset version information in `setup.py` to new next version + add back `[egg_info]` section
 * Add new empty section in `ChangeLog` for coming version

== Make releases ==

 * Checkout/export the freshly tagged code and use it to make releases.
 * Build docs (`./setup.py build_doc` and open doc/index.html in a browser to verify result).
 * Build and upload installers to FTP site in following formats and versions - for both 'Bitten' and 'Bitten-Slave':
   * .tar.gz (`sdist` *nix) and .zip (`sdist` Windows)
   * py26.egg (`bdist_egg` using any Python)
   * py25.egg (`bdist_egg` using any Python)
   * py24.egg (`bdist_egg` using any Python)
   * amd64.exe (`bdist_wininst` using 32-bit Windows Python)
   * .exe (`bdist_wininst` using 64-bit Windows Python)
 * Run `update-latest.sh` script in FTP directory to make 'latest' links and md5 checksums (also make a similar script for Bitten-Slave when that is ready)
 * Update wiki:Download page with new links

== Announce ==

Write an email to bitten mailing list.

== Questions... ==
 * What about PYPI? Entries for both Bitten and Bitten-Slave?