Raise the major version because the new release will return a different type of EntryPoint object which is owned by another library and has a different API from the type that used to be used. Change-Id: I901c31fae1ce870819682b1eaf34d6768e61d960 Signed-off-by: Doug Hellmann <firstname.lastname@example.org>
|10 hours ago|
|data||3 weeks ago|
|deliverables||10 hours ago|
|doc||1 week ago|
|openstack_releases||3 days ago|
|templates||9 months ago|
|tools||13 hours ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||1 month ago|
|CONTRIBUTING.rst||1 year ago|
|LICENSE||1 year ago|
|README.rst||8 months ago|
|bindep.txt||3 months ago|
|requirements.txt||1 month ago|
|setup.cfg||3 days ago|
|setup.py||5 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||2 months ago|
|watched_queries.yml||1 year ago|
|yamllint.yml||2 years ago|
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
For more information on how to use this repository, please read our reference documentation.
All official OpenStack software should go through the OpenStack 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).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.