59fa2b4480
This feature release brings in a couple of outward-facing changes: - The Adapter parameters ``connect_retries`` and ``status_code_retries`` can now be set via configuration options ``connect-retries`` and ``status-code-retries`` accordingly. [1] - The ``X-Openstack-Request-Id`` header can now be set per-request via a ``global_request_id`` kwarg to ``Adapter`` and ``Session`` request methods (``request()``, ``get()``, ``put()``, etc.) [2] [1] I67ba69bfff69676ceb28b8a7515f10f5eff21c4c [2] Ied73320fcd813ae796e40cbdb30717900486b92c Change-Id: Ie11383ac5c0dd2ee9b8a1730b7e365362e7c0084
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.