Start a new release cycle with empty release notes. The ABI version becomes 27.0. The ABI exceptions are dropped and CI ABI checks are disabled because compatibility is not preserved.
Signed-off-by: David Marchand <[email protected]> --- .github/workflows/build.yml | 4 +- ABI_VERSION | 2 +- VERSION | 2 +- devtools/libabigail.abignore | 7 -- doc/guides/rel_notes/index.rst | 1 + doc/guides/rel_notes/release_26_11.rst | 136 +++++++++++++++++++++++++ 6 files changed, 141 insertions(+), 11 deletions(-) create mode 100644 doc/guides/rel_notes/release_26_11.rst diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index f0ef39d34f..c63a9a3982 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -12,7 +12,7 @@ defaults: env: REF_GIT_BRANCH: main REF_GIT_REPO: https://github.com/DPDK/dpdk - REF_GIT_TAG: v26.03 + REF_GIT_TAG: none jobs: checkpatch: @@ -96,7 +96,7 @@ jobs: checks: stdatomic - os: ubuntu-22.04 compiler: gcc - checks: abi+debug+doc+examples+tests + checks: debug+doc+examples+tests - os: ubuntu-22.04 compiler: clang checks: asan+doc+tests diff --git a/ABI_VERSION b/ABI_VERSION index d38d431146..a0d6856dbe 100644 --- a/ABI_VERSION +++ b/ABI_VERSION @@ -1 +1 @@ -26.2 +27.0 diff --git a/VERSION b/VERSION index 403cc28f7a..a14edb8414 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -26.07.0 +26.11.0-rc0 diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore index 2a0efd718e..21b8cd6113 100644 --- a/devtools/libabigail.abignore +++ b/devtools/libabigail.abignore @@ -33,10 +33,3 @@ ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Temporary exceptions till next major ABI version ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; - -; Ignore new bit selective_rx in rte_eth_rxseg_capa bitmap hole -[suppress_type] - name = rte_eth_rxseg_capa - type_kind = struct - has_size_change = no - has_data_member_inserted_at = 6 diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst index 5771a3f47b..d39ee24449 100644 --- a/doc/guides/rel_notes/index.rst +++ b/doc/guides/rel_notes/index.rst @@ -8,6 +8,7 @@ Release Notes :maxdepth: 1 :numbered: + release_26_11 release_26_07 release_26_03 release_25_11 diff --git a/doc/guides/rel_notes/release_26_11.rst b/doc/guides/rel_notes/release_26_11.rst new file mode 100644 index 0000000000..938617ca75 --- /dev/null +++ b/doc/guides/rel_notes/release_26_11.rst @@ -0,0 +1,136 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2026 The DPDK contributors + +.. include:: <isonum.txt> + +DPDK Release 26.11 +================== + +.. **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. + + Variable and config names should be quoted as fixed width text: + ``LIKE_THIS``. + + Build the docs and view the output file to ensure the changes are correct:: + + ninja -C build doc + xdg-open build/doc/guides/html/rel_notes/release_26_11.html + + +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. + + Refer to the previous release notes for examples. + + Suggested order in release notes items: + * Core libs (EAL, mempool, ring, mbuf, buses) + * Device abstraction libs and PMDs (ordered alphabetically by vendor name) + - ethdev (lib, PMDs) + - cryptodev (lib, PMDs) + - eventdev (lib, PMDs) + - etc + * Other libs + * Apps, Examples, Tools (if significant) + + 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. + ======================================================= + + +API Changes +----------- + +.. This section should contain API changes. Sample format: + + * sample: Add a short 1-2 sentence description of the API change + which was announced in the previous releases and made in this release. + Start with a scope label like "ethdev:". + Use fixed width quotes for ``function_names`` or ``struct_names``. + Use 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. + ======================================================= + + +ABI Changes +----------- + +.. This section should contain ABI changes. Sample format: + + * sample: Add a short 1-2 sentence description of the ABI change + which was announced in the previous releases and made in this release. + Start with a scope label like "ethdev:". + Use fixed width quotes for ``function_names`` or ``struct_names``. + Use 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 title in present tense with full stop.** + + Add a short 1-2 sentence description of the known issue + in the present tense. Add information on any known workarounds. + + This section is a comment. Do not overwrite or remove it. + Also, make sure to start the actual text at the margin. + ======================================================= + + +Tested Platforms +---------------- + +.. This section should contain a list of platforms that were tested + with this release. + + The format is: + + * <vendor> platform with <vendor> <type of devices> combinations + + * List of CPU + * List of OS + * List of devices + * Other relevant details... + + This section is a comment. Do not overwrite or remove it. + Also, make sure to start the actual text at the margin. + ======================================================= -- 2.54.0
