diff mbox series

version: 22.03-rc0

Message ID 20211129131653.15301-1-david.marchand@redhat.com (mailing list archive)
State Superseded
Delegated to: David Marchand
Headers show
Series version: 22.03-rc0 | expand

Checks

Context Check Description
ci/intel-Testing success Testing PASS
ci/Intel-compilation success Compilation OK
ci/iol-aarch64-compile-testing success Testing PASS
ci/iol-x86_64-compile-testing success Testing PASS
ci/iol-x86_64-unit-testing success Testing PASS
ci/github-robot: build success github build: passed
ci/iol-aarch64-unit-testing success Testing PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/checkpatch warning coding style issues

Commit Message

David Marchand Nov. 29, 2021, 1:16 p.m. UTC
Start a new release cycle with empty release notes.
Bump version and ABI minor.
Enable ABI checks using latest libabigail.

Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 .github/workflows/build.yml            |   6 +-
 .travis.yml                            |  23 ++++-
 ABI_VERSION                            |   2 +-
 VERSION                                |   2 +-
 doc/guides/rel_notes/index.rst         |   1 +
 doc/guides/rel_notes/release_22_03.rst | 138 +++++++++++++++++++++++++
 6 files changed, 165 insertions(+), 7 deletions(-)
 create mode 100644 doc/guides/rel_notes/release_22_03.rst

Comments

Thomas Monjalon Nov. 30, 2021, 3:35 p.m. UTC | #1
29/11/2021 14:16, David Marchand:
> Start a new release cycle with empty release notes.
> Bump version and ABI minor.
> Enable ABI checks using latest libabigail.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
[...]
> -      LIBABIGAIL_VERSION: libabigail-1.8
> +      LIBABIGAIL_VERSION: libabigail-2.0

What is the reason for this update? Can we still use the old version?
Maybe add a small comment in the commit log.

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Thanks
David Marchand Nov. 30, 2021, 7:51 p.m. UTC | #2
On Tue, Nov 30, 2021 at 4:35 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 29/11/2021 14:16, David Marchand:
> > Start a new release cycle with empty release notes.
> > Bump version and ABI minor.
> > Enable ABI checks using latest libabigail.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> [...]
> > -      LIBABIGAIL_VERSION: libabigail-1.8
> > +      LIBABIGAIL_VERSION: libabigail-2.0
>
> What is the reason for this update? Can we still use the old version?

Nothing prevents from using the old version, I just used this chance
to bump the version.

I talked with Dodji, 2.0 is the version used in Fedora for ABI checks.
This version comes with enhancements and at least a fix for a bug we
got when writing exception rules in dpdk:
https://sourceware.org/bugzilla/show_bug.cgi?id=28060
David Marchand Dec. 2, 2021, 4:13 p.m. UTC | #3
On Tue, Nov 30, 2021 at 8:51 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Tue, Nov 30, 2021 at 4:35 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 29/11/2021 14:16, David Marchand:
> > > Start a new release cycle with empty release notes.
> > > Bump version and ABI minor.
> > > Enable ABI checks using latest libabigail.
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > [...]
> > > -      LIBABIGAIL_VERSION: libabigail-1.8
> > > +      LIBABIGAIL_VERSION: libabigail-2.0
> >
> > What is the reason for this update? Can we still use the old version?
>
> Nothing prevents from using the old version, I just used this chance
> to bump the version.
>
> I talked with Dodji, 2.0 is the version used in Fedora for ABI checks.
> This version comes with enhancements and at least a fix for a bug we
> got when writing exception rules in dpdk:
> https://sourceware.org/bugzilla/show_bug.cgi?id=28060

I ran more checks with 2.0 and unfortunately, I get an issue with dpdk
on Fedora 35 libabigail.
2.0 built in Ubuntu does not seem affected, but I prefer to be safe,
stick to 1.8 version and wait for Dodji to have a look.

v2 on the way.
diff mbox series

Patch

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 2e9c4be6d0..1a29e107be 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -20,10 +20,10 @@  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.0
       MINI: ${{ matrix.config.mini != '' }}
       PPC64LE: ${{ matrix.config.cross == 'ppc64le' }}
-      REF_GIT_TAG: none
+      REF_GIT_TAG: v21.11
       RUN_TESTS: ${{ contains(matrix.config.checks, 'tests') }}
 
     strategy:
@@ -40,7 +40,7 @@  jobs:
           - os: ubuntu-18.04
             compiler: gcc
             library: shared
-            checks: doc+tests
+            checks: abi+doc+tests
           - os: ubuntu-18.04
             compiler: clang
             library: static
diff --git a/.travis.yml b/.travis.yml
index 4bb5bf629e..da5273048f 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.0
+    - REF_GIT_TAG=v21.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 b090fe57f6..70a91e23ec 100644
--- a/ABI_VERSION
+++ b/ABI_VERSION
@@ -1 +1 @@ 
-22.0
+22.1
diff --git a/VERSION b/VERSION
index b570734337..25bb269237 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@ 
-21.11.0
+22.03.0-rc0
diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst
index 78861ee57b..876ffd28f6 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_22_03
     release_21_11
     release_21_08
     release_21_05
diff --git a/doc/guides/rel_notes/release_22_03.rst b/doc/guides/rel_notes/release_22_03.rst
new file mode 100644
index 0000000000..6d99d1eaa9
--- /dev/null
+++ b/doc/guides/rel_notes/release_22_03.rst
@@ -0,0 +1,138 @@ 
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright 2021 The DPDK contributors
+
+.. include:: <isonum.txt>
+
+DPDK Release 22.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_22_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 21.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.
+   =======================================================