Edgewall Software

Version 7 (modified by osimons, 15 years ago) (diff)

Minor details while fresh in memory...

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 first 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

  • Build docs for the tag
  • 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 win)
    • py26.egg (bdist_egg)
    • py25.egg (bdist_egg)
    • py24.egg (bdist_egg)
    • .exe (bdist_wininst)
  • 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?
  • Do we prepare releases for both Bitten and Bitten-Slave?
  • What source and egg versions do we need to prepare?