Go to file
Stephen Finucane 0777837c1d Ignore old 'vN-branch' tags when scanning for release notes
reno has an open TODO [1] to sort branches by something other than
alphabetical order. Unfortunately we're hitting this here since heat
previously had a 'vN-branch' branch naming scheme, and reno thinks those
branches are newer than e.g. 'stable/train'.

The solution is to just be stricter in how we select our branches and
tags, preventing those with hyphens in them from being accepted.

[1] https://github.com/openstack/reno/blob/3.0.0/reno/scanner.py#L850-L852

Change-Id: I75841d0dcb8e69214b7e96cf04f8b095da4d81d2
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2020-03-27 17:44:43 +00:00
2018-01-28 09:11:17 +05:30
2020-02-22 14:16:50 +08:00
2019-04-22 09:36:50 +05:30
2019-04-19 19:33:28 +00:00
2017-12-15 12:39:37 +05:30
2012-03-14 09:25:54 +11:00
2019-06-26 17:48:15 +02:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2019-12-19 15:25:30 +00:00
2016-01-17 05:20:40 +00:00

Team and repository tags

image

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://opendev.org/openstack/heat

Python client

Report a Story (a bug/blueprint)

If you'd like to report a Story (we used to call a bug/blueprint), you can report it under Report a story in Heat's StoryBoard. If you must report the story under other sub-project of heat, you can find them all in Heat StoryBoard Group. if you encounter any issue.

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 219 MiB
Languages
Python 99.5%
Shell 0.5%