Skip to content

Commit

Permalink
version: 25.03-rc0
Browse files Browse the repository at this point in the history
Start a new release cycle with empty release notes.
Bump version and ABI minor.
Bump libabigail from 2.4 to 2.6 and enable ABI checks.

Signed-off-by: David Marchand <[email protected]>
  • Loading branch information
david-marchand committed Nov 27, 2024
1 parent a4f4555 commit 4dcbf1d
Show file tree
Hide file tree
Showing 5 changed files with 145 additions and 6 deletions.
8 changes: 4 additions & 4 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ defaults:
env:
REF_GIT_BRANCH: main
REF_GIT_REPO: https://dpdk.org/git/dpdk
REF_GIT_TAG: none
REF_GIT_TAG: v24.11-rc4

jobs:
checkpatch:
Expand Down Expand Up @@ -46,7 +46,7 @@ jobs:
BUILD_EXAMPLES: ${{ contains(matrix.config.checks, 'examples') }}
CC: ccache ${{ matrix.config.compiler }}
DEF_LIB: ${{ matrix.config.library }}
LIBABIGAIL_VERSION: libabigail-2.4
LIBABIGAIL_VERSION: libabigail-2.6
MINGW: ${{ matrix.config.cross == 'mingw' }}
MINI: ${{ matrix.config.mini != '' }}
PPC64LE: ${{ matrix.config.cross == 'ppc64le' }}
Expand All @@ -69,7 +69,7 @@ jobs:
checks: stdatomic
- os: ubuntu-22.04
compiler: gcc
checks: debug+doc+examples+tests
checks: abi+debug+doc+examples+tests
- os: ubuntu-22.04
compiler: clang
checks: asan+doc+tests
Expand Down Expand Up @@ -133,7 +133,7 @@ jobs:
python3-pyelftools python3-setuptools python3-wheel zlib1g-dev
- name: Install libabigail build dependencies if no cache is available
if: env.ABI_CHECKS == 'true' && steps.libabigail-cache.outputs.cache-hit != 'true'
run: sudo apt install -y autoconf automake libdw-dev libtool libxml2-dev
run: sudo apt install -y autoconf automake libdw-dev libtool libxml2-dev libxxhash-dev
- name: Install i386 cross compiling packages
if: env.BUILD_32BIT == 'true'
run: sudo apt install -y gcc-multilib g++-multilib libnuma-dev:i386
Expand Down
2 changes: 1 addition & 1 deletion ABI_VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
25.0
25.1
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
24.11.0-rc4
25.03.0-rc0
1 change: 1 addition & 0 deletions doc/guides/rel_notes/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ Release Notes
:maxdepth: 1
:numbered:

release_25_03
release_24_11
release_24_07
release_24_03
Expand Down
138 changes: 138 additions & 0 deletions doc/guides/rel_notes/release_25_03.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,138 @@
.. SPDX-License-Identifier: BSD-3-Clause
Copyright 2024 The DPDK contributors
.. include:: <isonum.txt>

DPDK Release 25.03
==================

.. **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_25_03.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.
=======================================================
* No ABI change that would break compatibility with 24.11.


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.
=======================================================

0 comments on commit 4dcbf1d

Please sign in to comment.