This is internal documentation for Zope developers having to create official Zope releases.
The following persons have access to the
Zope package on PyPI
(in order to release new versions):
- Hanno Schlichting
- Michael Howitz
- Tres Seaver
- Jens Vagelpohl
Steps for creating a new Zope release¶
Create releases for the packages mentioned in buildout.cfg below
Check the versions.cfg file for outdated or updated packages and update version information where necessary:
$ bin/checkversions versions-prod.cfg $ bin/checkversions versions.cfg
There is no version pin for zc.buildout as it has to be installed in the virtual environment but checkversions also prints its version number.
There is no version pin for zc.recipe.egg in versions-prod.cfg as it is only needed for buildout install and not for pip, so we do not want to have it in requirements.txt.
The script is called two times so the rendered version updates can be easily assigned to the correct file.
Garden the change log.
Run the tests:
Update version information in change log and
Pin the Zope version in
Commit the changes.
Run all tests:
Check the future PyPI long description for ReST errors and for spelling issues:
Upload the tagged release to PyPI:
$ bin/release or $ git tag <TAG-NAME> $ bin/zopepy setup.py egg_info -RDb '' sdist bdist_wheel upload --sign
Update version information:
$ bin/postrelease $ vi versions-prod.cfg (remove Zope pin) $ bin/buildout
Commit and push the changes.
Check that the changes have been propagated to https://zope.readthedocs.io/en/latest/changes.html. (This should be done automatically via web hooks defined in GitHub and RTD.)
$ git checkout gh-pages $ ./build_index.sh
Add the newly created files and commit and push the changes.
Check on https://zopefoundation.github.io/Zope/ for the new release.