From: David Marchand Date: Wed, 27 May 2020 08:41:11 +0000 (+0200) Subject: version: 20.08-rc0 X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=27991115743bc0e1feb2c4ba7a766020d51bdb5d;p=dpdk.git version: 20.08-rc0 Start a new release cycle with empty release notes. Signed-off-by: David Marchand Acked-by: Thomas Monjalon --- diff --git a/.travis.yml b/.travis.yml index 2d2292ff64..14f8124233 100644 --- a/.travis.yml +++ b/.travis.yml @@ -36,7 +36,7 @@ script: ./.ci/${TRAVIS_OS_NAME}-build.sh env: global: - - REF_GIT_TAG=v20.02 + - REF_GIT_TAG=v20.05 jobs: include: diff --git a/ABI_VERSION b/ABI_VERSION index 204da679a1..a9ac8dacb0 100644 --- a/ABI_VERSION +++ b/ABI_VERSION @@ -1 +1 @@ -20.0.2 +20.0.3 diff --git a/VERSION b/VERSION index 4e3f998d00..30bbcd61a4 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -20.05.0 +20.08.0-rc0 diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst index 31278d2a8a..05c9d837a4 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_20_08 release_20_05 release_20_02 release_19_11 diff --git a/doc/guides/rel_notes/release_20_08.rst b/doc/guides/rel_notes/release_20_08.rst new file mode 100644 index 0000000000..39064afbe9 --- /dev/null +++ b/doc/guides/rel_notes/release_20_08.rst @@ -0,0 +1,139 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2020 The DPDK contributors + +.. include:: + +DPDK Release 20.08 +================== + +.. **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:: + + make doc-guides-html + + xdg-open build/doc/html/guides/rel_notes/release_20_08.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 + - 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 19.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. + =========================================================