Creating a release
This describes how to create a release tarball for MoinMoin. It's of minor interest to anyone except ThomasWaldmann. 
- find and fix any low hanging fruit left on the issue tracker
- check that Travis CI is happy
- make sure all issues for this milestone are closed or moved to the next milestone
- make install-docs interwiki
update the CHANGES file, based on git log $PREVIOUS_RELEASE..
- check version number / release data of upcoming release in CHANGES file
update version number in version.py and moin.spec, make sure there is no MoinMoin/patchlevel.py
- update the mig scripts to update data/meta file to the current version number
- make sure MANIFEST.in and setup.py is complete
update PO files:
cd MoinMoin/i18n PASS=xxx make update-po
- make underlay (on master, commit to repo)
- apply any pending fixes for security issues, update CHANGES file
git clone moin moin-rel
- touches all files so their mtime is current (maybe avoids trouble for people not using --force with setup.py)
- only stuff in the repo is in moin-rel dir, no other crap
Tag the release, e.g.: git tag -s -m "tagged/signed release X.Y.Z" X.Y.Z
- cd moin-rel ; make pagepacks ; make dist
- do some sanity checks on the release archive, fix as needed
Update https://pypi.org/project/moin/ by using make dist-release
Afterwards upload the tarball / signature that created to static.moinmo.in
- Create a Github release, include: pypi release file, signature, a link to CHANGES
Announcements: MoinMarketing/WhereToAnnounce
- Close release milestone on Github.