Jump to: navigation, search

Release-python-reddwarfclient

Redirect page

Releasing python-troveclient

Releasing python-troveclient is automated by Openstack Infra. There are a few Jenkins jobs that are set up on Openstack Jenkins that currently handle all aspects related to releasing a version.

There are two places the packages can end up.

  1. pypi.python.org
  2. tarballs.openstack.org

The release process is based on git tags that satisfy the following pattern: ^refs/tags/([0-9]+\.)+[0-9]*(alpha|beta|candidate|rc|a|b|c|r|g)[0-9]*$

NOTE: tags can only be pushed by members of 'trove-core'

Pre-Release Candidates

A pre-release candidate is a version that you don't want pushed to Pypi, but may want to make available as a package. These packages should go to tarballs.openstack.org.

When a tag is pushed to gerrit, that contains a non-numeric suffix, such as 'alpha1', 'beta4', 'rc', etc., a tarball is uploaded to tarballs.o.o.

(Regex to match: ([0-9]+\.)+[0-9]*(alpha|beta|candidate|rc|a|b|c|r|g)[0-9]*$)

Release Candidates

To release a new version to Pypi, a similar process should be followed. When a git tag does not contain a non-numeric suffix, '1.2.0', that package is uploaded to pypi.

(Regex to match: ([0-9]+\.)+[0-9]+$)