Thierry Carrez b6e5cb37c4 Revert "Increase tag-releases timeout"
This reverts commit e7a87665a8913f2927d2b3ca065086f79113d1a0
which triggered the following error:

Unable to freeze job graph:
Unable to modify final job <Job tag-releases branches: None
source: opendev/base-jobs/zuul.d/jobs.yaml@master#25>
attribute timeout=3600 with variant <Job tag-releases branches: None
source: openstack/releases/.zuul.yaml@master#10>

Change-Id: I70b2e3f25cecef42ccc7a4a991c52b5a6a4765fa
2019-10-24 12:44:33 +02: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
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 135 MiB
Languages
Python 89.2%
Shell 10.8%