From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 183A9A04DB; Mon, 30 Nov 2020 10:23:19 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8FC6D4F9A; Mon, 30 Nov 2020 10:23:16 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by dpdk.org (Postfix) with ESMTP id 8792537AF for ; Mon, 30 Nov 2020 10:23:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606728193; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=WOh/atU7Difuz4AFPbQrGL4vEXg66iDS9HmaV04FCqI=; b=ZjbE+LoR3my+jtjUcGlfUW6coRocWGx9PKw9S1IoVBlpeUR7wKM9Als1GRNdilioLkYdE0 RziuKkWtg9c3sVLaztSxjL93yDY9urtii4mtItd5dgxweYm7+V2UhSJi73YKq2q1/qxqB5 Tql+gH6bdZrU4s2i0PmK1DMY8QnEA6U= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-208-MdUJw81nMuanMnMchm_Qkg-1; Mon, 30 Nov 2020 04:23:10 -0500 X-MC-Unique: MdUJw81nMuanMnMchm_Qkg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 75A5D100E421; Mon, 30 Nov 2020 09:23:09 +0000 (UTC) Received: from dmarchan.remote.csb (unknown [10.40.193.97]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6EB835C1BB; Mon, 30 Nov 2020 09:23:08 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: thomas@monjalon.net Date: Mon, 30 Nov 2020 10:23:02 +0100 Message-Id: <20201130092302.8000-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=david.marchand@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII" Subject: [dpdk-dev] [PATCH] version: 21.02-rc0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Start a new release cycle with empty release notes. Signed-off-by: David Marchand --- Here we go again! Patches have been archived in patchwork, all deferred patches are back in the NEW state. I'll send a separate patch to re-enable the ABI checks in the CI. Please maintainers, rebase your trees. The current dates for this release: - Proposal deadline (RFC/v1 patches): December 20, 2020 - API freeze (-rc1): January 15, 2021 - Release: February 5, 2021 --- ABI_VERSION | 2 +- VERSION | 2 +- doc/guides/rel_notes/index.rst | 1 + doc/guides/rel_notes/release_21_02.rst | 139 +++++++++++++++++++++++++ 5 files changed, 143 insertions(+), 3 deletions(-) create mode 100644 doc/guides/rel_notes/release_21_02.rst diff --git a/ABI_VERSION b/ABI_VERSION index 204da679a1..a9ac8dacb0 100644 --- a/ABI_VERSION +++ b/ABI_VERSION @@ -1 +1 @@ -21.0 +21.1 diff --git a/VERSION b/VERSION index 4e3f998d00..30bbcd61a4 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -20.11.0 +21.02.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_21_02 release_20_11 release_20_08 release_20_05 diff --git a/doc/guides/rel_notes/release_21_02.rst b/doc/guides/rel_notes/release_21_02.rst new file mode 100644 index 0000000000..39064afbe9 --- /dev/null +++ b/doc/guides/rel_notes/release_21_02.rst @@ -0,0 +1,139 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2020 The DPDK contributors + +.. include:: + +DPDK Release 21.02 +================== + +.. **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_21_02.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 20.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. + ========================================================= -- 2.23.0