= 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
 * Before major releases:
   * `svn copy trunk -> /branches/<major>.x`
   * Initialize merge-tracking from trunk to new branch

== Tag release ==

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

== 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
 * If `ChangeLog` changed in branch, also update in trunk

== Make releases ==

 * Upload to Downloads and FTP installers in following formats and versions:
   * .tar.gz
   * py26.egg
   * py25.egg
   * py24.egg

== Announce ==

Write an email to bitten mailing list.

== Questions... ==
 * What about pypi entries?
 * Do we prepare releases for both Bitten and Bitten-Slave?