Release Process#

Release Cadence and Versions#

After gevent 1.5, gevent releases switched to CalVer, using the scheme YY.0M.Micro (two-digit year, zero-padded month, micro/patch number). Thus the first release in April of 2020 would be version 20.04.0. A second release would be 20.04.1, etc. The first release in May would be 20.05.0, and so on.

If there have been changes to master, gevent should produce a release at least once a month.

Deprecation Policy#

Any change to gevent that removes or significantly alters user-visible behavior that is described in the gevent documentation will be deprecated for a minimum of 6 months before the change occurs. Deprecation will be called out in the documentation and in some cases with a runtime warning when the feature is used (because of the performance sensitive nature of gevent, not all deprecations will have a runtime warning). Longer deprecation periods, or deprecation warnings for behavior changes that would not normally be covered by this policy, are also possible depending on circumstances, but this is at the discretion of the gevent developers.

Note that the documentation is the sole reference for what counts as agreed behavior. If something isn’t explicitly mentioned in the documentation, it can be changed without warning, or any deprecation period, in a gevent release. However, we are aware that the documentation isn’t always complete - PRs that document existing behavior with the intention of covering that behavior with the above deprecation process are always acceptable, and will be considered on their merits.

Releasing gevent#


This is a semi-organized collection of notes for gevent maintainers.

gevent is released using zest.releaser. Binary wheels are published automatically by Github Actions CI (macOS and manylinux) and Appveyor (Windows) when a tag is uploaded.

  1. Push all relevant changes to master.

  2. From the gevent working copy, run fullrelease. Fix any issues it brings up. Let it bump the version number (or enter the correct one), commit, create the tag, create the sdist, upload the sdist and push the tag to GitHub.

  3. Monitor the build process on the CI systems. If particular builds fail due to test instability, re-run them to allow the binary wheel to be uploaded.