Switch branches/tags
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
90 lines (54 sloc) 1.97 KB

Maintenance information


This is internal documentation for Zope developers having to create official Zope releases.

Release process


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 auto-checkout.

  • Check the versions.cfg file for outdated or updated packages and update version information where necessary:

    $ bin/checkversions buildout.cfg
  • Run the tests:

    $ bin/tox
  • Update version information in change log and

    $ bin/prerelease
  • Pin the Zope version in versions-prod.cfg.

  • Run bin/buildout to update requirements-full.txt and constraints.txt.

  • Commit the changes.

  • Run all tests:

    $ bin/tox
  • Check the future PyPI long description for ReST errors and for spelling issues:

    $ bin/longtest
  • Upload the tagged release to PyPI:

    $ git tag <TAG-NAME>
    $ bin/zopepy egg_info -RDb '' sdist bdist_wheel upload --sign
    $ bin/release
  • Update version information:

    $ bin/postrelease
    $ vi versions-prod.cfg (remove Zope pin)
    $ bin/buildout
  • Commit and push the changes.

  • Check the visible releases on at (should default to showing the active branches):
  • Update (This is needed until is fixed.):

    $ git checkout gh-pages
    $ ./
  • Add the newly created files and commit and push the changes.

  • Check on for the new release.

  • Announce the release to the world via and