Go to file
Ghanshyam Mann af26e0d9dd Remove the stable/stein branch for Patrole
Patrole is branchless with "cycle-with-intermediary" model
and does not create the stable branch with same reason as
Tempest.

Below commit added the stable/stein for Patrole which is not
correct- https://review.opendev.org/#/c/650173

This commit removes the branching from stein patrole release.

As next step, we will add some type(as proposed by ttx[1]) or
tag to make it clear that Patrole does not need branch.

[1] https://review.opendev.org/#/c/670808/

Change-Id: Ib11838bc87e4fe0a350d107184be68e837233891
2019-07-16 04:03:44 +00:00
2019-07-01 14:54:16 +01:00
2019-07-08 11:40:11 -05: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
2019-06-19 16:22:29 -07:00
2018-07-10 10:38:33 +07:00
2019-04-18 15:27:27 +10: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 141 MiB
Languages
Python 89.1%
Shell 10.9%