summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPierre Riteau <pierre@stackhpc.com>2020-02-12 17:28:44 +0100
committerzhurong <aaronzhu1121@gmail.com>2020-02-26 00:49:02 +0000
commitaf40e1bf360dbadb6e064c116c8bd5e58e650878 (patch)
tree34d63f95b36c896d73f1cd860853c3e8260c01c7
parent010dae0094c16a704dedb72b17956a4d9c2050ca (diff)
downloadceilometer-rocky-em.tar.gz
Tell reno to ignore the kilo branchrocky-em11.1.0
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: I8047d805b0a3da4051a6d618ed9ac40875b8636a Co-Authored-By: Doug Hellmann <doug@doughellmann.com> Story: 2007274 Task: 38749 (cherry picked from commit 8770b9223005a52c5270556606be43909895b9f3) (cherry picked from commit 4e91fa56d12866f81b820244f9125c2da4fa762a) (cherry picked from commit e3988d2c45d084ab119d56facfdd5d47aca315a4)
-rw-r--r--reno.yaml4
1 files changed, 4 insertions, 0 deletions
diff --git a/reno.yaml b/reno.yaml
new file mode 100644
index 00000000..dd0aac79
--- /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: "(.+)(?<!kilo)-eol"