From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [PATCH] version: 23.07-rc0
Date: Fri, 28 Apr 2023 15:14:05 +0800 [thread overview]
Message-ID: <20230428071405.686993-1-lijuan.tu@intel.com> (raw)
Start a new release cycle with empty release notes.
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
doc/dts_gsg/rel_notes/index.rst | 1 +
doc/dts_gsg/rel_notes/release_23_07.rst | 65 +++++++++++++++++++++++++
version.py | 4 +-
3 files changed, 68 insertions(+), 2 deletions(-)
create mode 100644 doc/dts_gsg/rel_notes/release_23_07.rst
diff --git a/doc/dts_gsg/rel_notes/index.rst b/doc/dts_gsg/rel_notes/index.rst
index 803347e2..694ad0b3 100644
--- a/doc/dts_gsg/rel_notes/index.rst
+++ b/doc/dts_gsg/rel_notes/index.rst
@@ -7,6 +7,7 @@ Release Notes
.. toctree::
:maxdepth: 1
+ release_23_07
release_23_03
release_22_11
release_22_07
diff --git a/doc/dts_gsg/rel_notes/release_23_07.rst b/doc/dts_gsg/rel_notes/release_23_07.rst
new file mode 100644
index 00000000..e9240b23
--- /dev/null
+++ b/doc/dts_gsg/rel_notes/release_23_07.rst
@@ -0,0 +1,65 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+ Copyright 2023 The DTS contributors
+
+DTS Release 23.07
+=================
+
+.. **Read this first.**
+
+ The text in the sections below explains how to update the release notes.
+
+ Use proper spelling, capitalization and punctuation in all sections.
+
+
+New Features
+------------
+
+.. This section should contain new features added in this release.
+
+ Sample format:
+
+ * **Add a title in the past tense with a full stop.**
+
+ Add a short 1-2 sentence description in the past tense.
+ The description should be enough to allow someone scanning
+ the release notes to understand the new feature.
+
+ If the feature adds a lot of sub-features you can use a bullet list
+ like this:
+
+ * Added feature foo to do something.
+ * Enhanced feature bar to do something else.
+
+ This section is a comment. Do not overwrite or remove it.
+ Also, make sure to start the actual text at the margin.
+ =======================================================
+
+
+Removed Items
+-------------
+
+.. This section should contain removed items in this release.
+
+ Sample format:
+
+ * Add a short 1-2 sentence description of the removed item
+ in the past tense.
+
+ This section is a comment. Do not overwrite or remove it.
+ Also, make sure to start the actual text at the margin.
+ =======================================================
+
+
+Known Issues
+------------
+
+.. This section should contain new known issues in this release.
+
+ Sample format:
+
+ * Add a short 1-2 sentence description of the removed item
+ in the past tense.
+
+ This section is a comment. Do not overwrite or remove it.
+ Also, make sure to start the actual text at the margin.
+ =======================================================
diff --git a/version.py b/version.py
index 2efe92c6..1550a304 100755
--- a/version.py
+++ b/version.py
@@ -1,9 +1,9 @@
# <COPYRIGHT_TAG>
VERSION_MAJOR = "23"
-VERSION_MINOR = "03"
+VERSION_MINOR = "07"
VERSION_PATCH = "0"
-VERSION_EXTRA = ""
+VERSION_EXTRA = "rc0"
__version__ = "%s.%s.%s" % (VERSION_MAJOR, VERSION_MINOR, VERSION_PATCH)
--
2.25.1
next reply other threads:[~2023-04-28 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 7:14 Lijuan Tu [this message]
2023-04-28 12:48 ` lijuan.tu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230428071405.686993-1-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).