This list describes the release procedure for PyInstaller.

This page has still to be rewritten to reflect the new workflow, as described in Development/WorkflowBranchingMergingTagging.

Preparation

1. Discuss plan for next release in mailing list.
2. Create new milestone.
3. Assign new tickets to this milestone.
4. Implement and close all tickets in a specific milestone.

Release

1. Be sure that the current code configures and compiles.
2. Recompile binary bootloaders for every supported OS (32bit and 64bit)
   • Windows: Visual Studio 2008
   • Linux:LSB 4.0
   • Mac OS X: gcc in Mac
3. Run tests on Win, Linux and Mac (32bit and 64bit) with different python versions.
4. Update doc/CHANGES.txt file.
5. Update the manual and man pages. Commit these changes.
6. Remove dev from version in PyInstaller.__init__.py and doc/source/_definitions.txt
7. Build html and pdf manuals with new version: make -C doc/source/ doc
8. Optional: Build binaries of some real app with new version
9. Commit everything to svn.
10. Create branch for the release with name X.Y where X is major version and Y minor version number.
11. Export the checkout by svn export to ensure that everything is there and all .svn files are removed.
12. Build release files (.tgz, .zip, ...).
13. Tag the release.
14. Test release files.
15. Upload release files to www.pyinstaller.org/static/source/X.Y
16. Update website, wiki, FAQ
17. Announce new release on:
    • ​!PyInstaller Mailing List
    • ​Freshmeat
    • ​PyPi
18. Update Trac with new version number for bug reporting for this new version.
19. Increment PyInstaller version in trunk, append 'dev' to it and commit change as "Post-release version bump."