Go to file
Hervé Beraud d63b38783a Fix a bug on list_unreleased_changes during tag retrieving
Indeed `gitutils.gitutils.stable_branch_exists` is waiting for a branch
name not prefixed with `stable/`. This was not an issue with the
previous shell version. These changes fix that.

Without these changes the master branch will be analyzed and stable
branches will be ignored.

Change-Id: I61542508e8566eb797b0e304a6914d25e3b07e14
2020-07-27 22:04:08 +02:00
2020-07-24 09:46:28 +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
2020-06-02 14:28:30 -05:00
2020-04-11 15:57:21 -05:00
2018-10-17 10:36:04 +11:00
2019-11-13 16:51:02 +01:00
2020-05-10 17:42:14 -05:00

OpenStack Releases

image

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.

More information

You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.

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