Checks
Commit Message
Start a new release cycle with empty release notes.
Bump version and ABI minor.
Signed-off-by: David Marchand <david.marchand@redhat.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
---
.github/workflows/build.yml | 2 +-
.travis.yml | 2 +-
ABI_VERSION | 2 +-
VERSION | 2 +-
doc/guides/rel_notes/index.rst | 1 +
doc/guides/rel_notes/release_22_07.rst | 138 +++++++++++++++++++++++++
6 files changed, 143 insertions(+), 4 deletions(-)
create mode 100644 doc/guides/rel_notes/release_22_07.rst
Comments
David Marchand <david.marchand@redhat.com> writes:
> Start a new release cycle with empty release notes.
> Bump version and ABI minor.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Aaron Conole <aconole@redhat.com>
18/03/2022 15:35, David Marchand:
> +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.
Should we say 21.11 and 22.03?
On Mon, Mar 21, 2022 at 2:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 18/03/2022 15:35, David Marchand:
> > +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.
>
> Should we say 21.11 and 22.03?
In practice, compatibility is probably maintained, but we are
committed to maintain ABI compatibility with v21.11 only.
So I would leave this as is.
http://inbox.dpdk.org/dev/27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu/
18/03/2022 16:46, Aaron Conole:
> David Marchand <david.marchand@redhat.com> writes:
>
> > Start a new release cycle with empty release notes.
> > Bump version and ABI minor.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Aaron Conole <aconole@redhat.com>
Applied, thanks
David Marchand <david.marchand@redhat.com> writes:
> On Mon, Mar 21, 2022 at 2:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>>
>> 18/03/2022 15:35, David Marchand:
>> > +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.
>>
>> Should we say 21.11 and 22.03?
>
> In practice, compatibility is probably maintained, but we are
> committed to maintain ABI compatibility with v21.11 only.
> So I would leave this as is.
>
> http://inbox.dpdk.org/dev/27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu/
Agreed +1 - our only commitment is to v21.11.
Otherwise things would start to get very complicated. :-)
22/03/2022 10:15, Ray Kinsella:
> David Marchand <david.marchand@redhat.com> writes:
> > On Mon, Mar 21, 2022 at 2:01 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >> 18/03/2022 15:35, David Marchand:
> >> > +* No ABI change that would break compatibility with 21.11.
> >>
> >> Should we say 21.11 and 22.03?
> >
> > In practice, compatibility is probably maintained, but we are
> > committed to maintain ABI compatibility with v21.11 only.
> > So I would leave this as is.
> >
> > http://inbox.dpdk.org/dev/27c97b09-0b78-ccbc-db1e-860ac6012aec@ashroe.eu/
>
> Agreed +1 - our only commitment is to v21.11.
> Otherwise things would start to get very complicated. :-)
I don't think it would be more complicated.
In reality, we are already testing compatibility with minor versions,
and there is no issue.
@@ -23,7 +23,7 @@ jobs:
LIBABIGAIL_VERSION: libabigail-1.8
MINI: ${{ matrix.config.mini != '' }}
PPC64LE: ${{ matrix.config.cross == 'ppc64le' }}
- REF_GIT_TAG: v21.11
+ REF_GIT_TAG: v22.03
RUN_TESTS: ${{ contains(matrix.config.checks, 'tests') }}
strategy:
@@ -42,7 +42,7 @@ script: ./.ci/${TRAVIS_OS_NAME}-build.sh
env:
global:
- LIBABIGAIL_VERSION=libabigail-1.8
- - REF_GIT_TAG=v21.11
+ - REF_GIT_TAG=v22.03
jobs:
include:
@@ -1 +1 @@
-22.1
+22.2
@@ -1 +1 @@
-22.03.0
+22.07.0-rc0
@@ -8,6 +8,7 @@ Release Notes
:maxdepth: 1
:numbered:
+ release_22_07
release_22_03
release_21_11
release_21_08
new file mode 100644
@@ -0,0 +1,138 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+ Copyright 2022 The DPDK contributors
+
+.. include:: <isonum.txt>
+
+DPDK Release 22.07
+==================
+
+.. **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_07.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.
+ =======================================================