Difference between revisions of "Release-python-reddwarfclient"
m (→Pre-Release Candidates) |
(Redirected page to Trove/release-python-troveclient) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | == Releasing python- | + | #REDIRECT [[trove/release-python-troveclient]] |
| − | Releasing python- | + | == 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. | There are two places the packages can end up. | ||
| Line 9: | Line 10: | ||
''^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 ' | + | NOTE: tags can only be pushed by members of 'trove-core' |
==== Pre-Release Candidates ==== | ==== Pre-Release Candidates ==== | ||
| Line 22: | Line 23: | ||
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. | 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]+$) | ||
Latest revision as of 23:05, 8 July 2013
Redirect to:
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.
- 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 '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]+$)
