9e8c15914d
Note that this is the metapackage that installs python-openstackclient and all of the plugins listed in requirements.txt at one time for user convenience. This is the first real release of this package, we are using major version 4 to correspond to the major version of python-openstackclient version that will be installed. We want to maintain that consistency for the major version only and anticipate that the only other reason for releases will be for adjusting the plugin list and their version requirements and do not intend to match more than the major version with the primary OSC package. Change-Id: Ic9c1e189385ec58fe834897f46dfbffbc00b1bb7 Signed-off-by: Dean Troyer <dtroyer@gmail.com> |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
Using This Repository
All official OpenStack software should go through the Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.