diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 82d83f4030..9527ad1f8c 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -21,11 +21,11 @@ jobs: BUILD_DOCS: ${{ contains(matrix.config.checks, 'doc') }} CC: ccache ${{ matrix.config.compiler }} DEF_LIB: ${{ matrix.config.library }} - LIBABIGAIL_VERSION: libabigail-1.8 + LIBABIGAIL_VERSION: libabigail-2.1 MINGW: ${{ matrix.config.cross == 'mingw' }} MINI: ${{ matrix.config.mini != '' }} PPC64LE: ${{ matrix.config.cross == 'ppc64le' }} - REF_GIT_TAG: none + REF_GIT_TAG: v22.11 RISCV64: ${{ matrix.config.cross == 'riscv64' }} RUN_TESTS: ${{ contains(matrix.config.checks, 'tests') }} @@ -38,7 +38,7 @@ jobs: mini: mini - os: ubuntu-20.04 compiler: gcc - checks: doc+tests + checks: abi+doc+tests - os: ubuntu-20.04 compiler: clang checks: asan+doc+tests diff --git a/.travis.yml b/.travis.yml index 4bb5bf629e..b99444620f 100644 --- a/.travis.yml +++ b/.travis.yml @@ -41,8 +41,8 @@ script: ./.ci/${TRAVIS_OS_NAME}-build.sh env: global: - - LIBABIGAIL_VERSION=libabigail-1.8 - - REF_GIT_TAG=none + - LIBABIGAIL_VERSION=libabigail-2.1 + - REF_GIT_TAG=v22.11 jobs: include: @@ -61,6 +61,14 @@ jobs: packages: - *required_packages - *doc_packages + - env: DEF_LIB="shared" ABI_CHECKS=true + arch: amd64 + compiler: gcc + addons: + apt: + packages: + - *required_packages + - *libabigail_build_packages # x86_64 clang jobs - env: DEF_LIB="static" arch: amd64 @@ -137,6 +145,17 @@ jobs: packages: - *required_packages - *doc_packages + - env: DEF_LIB="shared" ABI_CHECKS=true + dist: focal + arch: arm64-graviton2 + virt: vm + group: edge + compiler: gcc + addons: + apt: + packages: + - *required_packages + - *libabigail_build_packages # aarch64 clang jobs - env: DEF_LIB="static" dist: focal diff --git a/ABI_VERSION b/ABI_VERSION index 919c868b57..a12b18e437 100644 --- a/ABI_VERSION +++ b/ABI_VERSION @@ -1 +1 @@ -23.0 +23.1 diff --git a/VERSION b/VERSION index 7af24b7ddb..61240e02c2 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -22.11.0 +23.03.0-rc0 diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst index f6782b91db..57475a8158 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_23_03 release_22_11 release_22_07 release_22_03 diff --git a/doc/guides/rel_notes/release_23_03.rst b/doc/guides/rel_notes/release_23_03.rst new file mode 100644 index 0000000000..b8c5b68d6c --- /dev/null +++ b/doc/guides/rel_notes/release_23_03.rst @@ -0,0 +1,138 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2022 The DPDK contributors + +.. include:: + +DPDK Release 23.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_23_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 22.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: + + * platform with 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. + =======================================================