From 175cb0b642337d01c0466c8ff0409bcb09b8e3eb Mon Sep 17 00:00:00 2001 From: Kristi Nikolla Date: Fri, 21 Feb 2020 13:44:11 -0500 Subject: [PATCH] Tell reno to ignore the kilo branch This patch was adopted from Idd56c3f37d5786daae7181c36d38d267cbf1885c Original description: When reno 3.x runs under setuptools, it scans all of the branches it can find, including any that look like they're closed and have an -eol tag. The old kilo branch in this repository has a jumbled history that somehow makes it look like it should include tags that it doesn't. We know that there are no release notes in that branch, because reno wasn't adopted while it was open. The releasenotes/source/index.rst links to separate release notes in the wiki. This patch tells reno to ignore that branch so that it doesn't throw an exception when it gets confused about the old tag. Change-Id: I28fd0fd499c40e33ff164fd643dadd6ac9009b17 Co-Authored-By: Doug Hellmann Co-Authored-By: Sean McGinnis --- .gitignore | 2 ++ reno.yaml | 4 ++++ 2 files changed, 6 insertions(+) create mode 100644 reno.yaml diff --git a/.gitignore b/.gitignore index 3fca82f27d..4a14de2d7e 100644 --- a/.gitignore +++ b/.gitignore @@ -34,6 +34,8 @@ keystone/locale/*/LC_MESSAGES/*.mo *.db # Files created by releasenotes build releasenotes/build +RELEASENOTES.rst +releasenotes/notes/reno.cache # sample config included in docs doc/source/_static/keystone.conf.sample etc/keystone.conf.sample diff --git a/reno.yaml b/reno.yaml new file mode 100644 index 0000000000..dd0aac790b --- /dev/null +++ b/reno.yaml @@ -0,0 +1,4 @@ +--- +# Ignore the kilo-eol tag because that branch does not work with reno +# and contains no release notes. +closed_branch_tag_re: "(.+)(?