This transition the Train branch to End of Life. The last patch of the branch will be tagged with train-eol tag. The stable/train branch cannot be used anymore and will be deleted if this patch merges. This is needed as stable/train is not actively maintained in the recent period and thus gates are broken due to job failures. Please try to identify any zuul job, that is defined outside of the repositories in this patch (for example in openstack-zuul-jobs, etc.) and won't be used anymore if stable/train is deleted, and propose a job removal patch for them. Please +1 if the team is ready for us to proceed with this transition, or -1 if there are still some activity on the branch and the team wants to continue to maintain it. Change-Id: I425a77304b6b1dd70e16ec69e349330d8f6eec11
|6 months ago|
|data||6 months ago|
|deliverables||6 months ago|
|doc||7 months ago|
|openstack_releases||8 months ago|
|templates||4 years ago|
|tools||1 year ago|
|.gitignore||5 years ago|
|.gitreview||4 years ago|
|.stestr.conf||5 years ago|
|.zuul.yaml||10 months ago|
|CONTRIBUTING.rst||2 years ago|
|LICENSE||5 years ago|
|README.rst||2 years ago|
|bindep.txt||3 years ago|
|requirements.txt||10 months ago|
|setup.cfg||1 year ago|
|setup.py||7 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||1 year ago|
|watched_queries.yml||4 years ago|
|yamllint.yml||6 years ago|
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.