summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGhanshyam Mann <gmann@ghanshyammann.com>2023-02-19 16:53:55 -0800
committerGhanshyam <gmann@ghanshyammann.com>2023-02-25 02:53:28 +0000
commit50d52e239e91b588fba8697989d3cb371fd95b9b (patch)
treeff6285ab07a86589d651f8e23630cb8bc556f2d6
parent8f4a22141ea06a0a02c41b1dd2c11e8901db90d3 (diff)
downloadtempest-50d52e239e91b588fba8697989d3cb371fd95b9b.tar.gz
Add releasenote to tag the Tempest for 2023.1 release
Change-Id: I11996f06bd17cdce4ee2313e4604474591c466a5
-rw-r--r--releasenotes/notes/tempest-2023-1-release-b18a240afadae8c9.yaml17
1 files changed, 17 insertions, 0 deletions
diff --git a/releasenotes/notes/tempest-2023-1-release-b18a240afadae8c9.yaml b/releasenotes/notes/tempest-2023-1-release-b18a240afadae8c9.yaml
new file mode 100644
index 000000000..092f4e313
--- /dev/null
+++ b/releasenotes/notes/tempest-2023-1-release-b18a240afadae8c9.yaml
@@ -0,0 +1,17 @@
+---
+prelude: |
+ This release is to tag Tempest for OpenStack 2023.1 release.
+ This release marks the start of 2023.1 release support in Tempest.
+ After this release, Tempest will support below OpenStack Releases:
+
+ * 2023.1
+ * Zed
+ * Yoga
+ * Xena
+
+ Current development of Tempest is for OpenStack 2023.2 development
+ cycle. Every Tempest commit is also tested against master during
+ the 2023.2 cycle. However, this does not necessarily mean that using
+ Tempest as of this tag will work against a 2023.2 (or future release)
+ cloud.
+ To be on safe side, use this tag to test the OpenStack 2023.1 release.