Go to file
Dmitriy Rabotyagov 529190ddfa Allow upper-constraints redirect based on SHA
This patch aims to make possible to provide SHA commit
for https://releases.openstack.org/constraints/upper/ URL
in addition to branch or tag. This is heavily used by OSA to be sure
that every time role is runned under some release it will install
the same package versions.
And to be consistent and use releases.openstack.org for contraints
not only in tox but in role itself this patch is needed.

Change-Id: I1ce0af2ab2163ea1f154516229889b3cf8813ab6
2019-10-28 14:31:29 +00:00
2019-09-23 18:04:44 +02:00
2018-07-10 10:38:33 +07:00
2019-04-19 19:37:48 +00:00
2018-07-10 10:38:33 +07:00
2019-10-10 17:21:26 -05:00
2018-10-17 10:36:04 +11:00
2018-07-10 10:38:33 +07:00
2019-08-08 09:50:12 +00:00

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.

image

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.

Description
Release requests and history tracking
Readme 142 MiB
Languages
Python 89.1%
Shell 10.9%