Difference between revisions of "Release-python-reddwarfclient"
(→Pre-Release Candidates) |
(→Releasing python-reddwarfclient) |
||
| Line 8: | Line 8: | ||
The release process is based on git tags that satisfy the following pattern: | 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]*$'' | ''^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 'reddwarf-core' | ||
==== Pre-Release Candidates ==== | ==== Pre-Release Candidates ==== | ||
Revision as of 20:00, 12 March 2013
Releasing python-reddwarfclient
Releasing python-reddwarfclient 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.
- pypi.python.org
- 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 'reddwarf-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.
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.
