This page is intended to document the release process of Stackless Python.
- Run the Python standard library unit tests with CPython to get a base line.
- Compile with STACKLESS_OFF, run Python standard library unit tests.
- Compile with STACKLESS.
- Run the Python standard library unit tests with debug and regular builds.
- Run the Stackless Python unit tests with debug and regular builds.
- If compiling and running on Windows, repeat on Linux.
- Update Stackless/changelog.txt: add the release date, add missing changes.
- Tag the release.
- Push to bitbucket.
- Generate a tarball using Anselm's zip archive generation script in stackless/Stackless/Tools/create_source_archive.sh. See below for details.
- Upload to stackless.com/binaries/.
- Find someone to generate the 32 & 64 bit msi installers. Anselm can do that.
- Find someone to generate the MacOS installer. Do not block on this step if not possible.
- Announce: update the download page and archived downloads page.
How to Create a Stackless Python Source Code Archive
Unfortunately it is not enough to simply run hg archive .... The reason is, that the archive contains a few generated files together with their source files:
Sources are in Parser/.
Building theses files requires Python itself; a classical chicken and eggs problem. Therefore it is essential that the timestamps of generated files are newer that the timestamps of their sources after unpacking the source archive. This requires not only to touch generated files prior to packaging but also to control the order of archive members.
Use the script stackless/Stackless/Tools/create_source_archive.sh to create a source archive.