From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [PATCH v2] doc: announce new major ABI version
Date: Fri, 28 Jul 2023 17:18:40 +0200 [thread overview]
Message-ID: <20230728152052.1204486-1-thomas@monjalon.net> (raw)
In-Reply-To: <20230728142946.1201459-1-thomas@monjalon.net>
The next DPDK release 23.11 won't keep ABI compatibility.
Only the changes impacting the users should be announced in advance.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
v2: improve wording (thanks Bruce)
---
doc/guides/rel_notes/deprecation.rst | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 91ac8f0229..18281d7304 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -4,9 +4,15 @@
ABI and API Deprecation
=======================
-See the guidelines document for details of the :doc:`ABI policy
-<../contributing/abi_policy>`. API and ABI deprecation notices are to be posted
-here.
+See the guidelines document for details
+of the :doc:`ABI policy <../contributing/abi_policy>`.
+
+With DPDK 23.11, there will be a new major ABI version: 24.
+This means that during the development of 23.11,
+new items may be added to structs or enums,
+even if those additions involve an ABI compatibility breakage.
+
+Other API and ABI deprecation notices are to be posted below.
Deprecation Notices
-------------------
--
2.41.0
next prev parent reply other threads:[~2023-07-28 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 14:29 [PATCH] " Thomas Monjalon
2023-07-28 15:18 ` Thomas Monjalon [this message]
2023-07-28 15:23 ` [PATCH v2] " Bruce Richardson
2023-07-28 16:03 ` Thomas Monjalon
2023-07-28 17:02 ` Patrick Robb
2023-07-28 17:33 ` Thomas Monjalon
2023-07-31 4:42 ` [EXT] " Akhil Goyal
2023-07-28 15:25 ` Morten Brørup
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=20230728152052.1204486-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@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).