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 AE3F3A04B5; Mon, 2 Dec 2019 15:57:31 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7CCFC1BF71; Mon, 2 Dec 2019 15:57:31 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 80F971BF6F for ; Mon, 2 Dec 2019 15:57:29 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 1DE5C123B; Mon, 2 Dec 2019 09:57:28 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 02 Dec 2019 09:57:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=mesmtp; bh=n7gxnJF0fQl23dTb0wCih3M kqZPH4LyvuNdw/Eix1VU=; b=r9wjY1uzGCWgndOwFrxHJp0I3x280GJgAXwTMk+ EpXc5m58FX6GBkDcPPPFwbxXfNeN/iO+owqTBodkV1MNTFFhe3UhSRNcuTF4Xds7 vjz2RgOG1TYvd22dhkxikQRjkL0XydcBX9EFsutCUdaVbtaozCTefotrCuCrBg2K d0Zg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=n7gxnJF0fQl23dTb0 wCih3MkqZPH4LyvuNdw/Eix1VU=; b=VznRb3I1nqTSdIapl1zZ8RYQ25WgSuYJg Nuvrq6IFI6pgK03FlTYfx3HlgvesRYu8y/KaFC5R0hHwCYkdTo5tStNF51WFnskG LpWeJ8SBFICKSr9OsYqulD8HyGtdJG7SgeT15YJrSZOIOhhVKl9JnBPmXyQS+jVY K64yWPfa3ws9530HUaRqXI/GPANBVzWiSbrEqFOx8nxt43rm5jxPhDxEAHJFcfNX ru7v9fRGTSyMxGEDvZtT1glyJeAHcMSPWEfjz4EidwafKgXr5uofEdiTUIonTnGq 8s5Ulwdrs+gdvgOJ0dekyLYsowbw1Cn1+uShFzwEBCZ5dqpXqjgsg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejhedgjeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkffoggfgsedtkeertdertddtnecuhfhrohhmpefvhhhomhgrshcu ofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppe ejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhm rghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A7E9B30600BD; Mon, 2 Dec 2019 09:57:26 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org Cc: David Marchand , Neil Horman , Ray Kinsella Date: Mon, 2 Dec 2019 15:57:18 +0100 Message-Id: <20191202145718.16407-1-thomas@monjalon.net> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH] version: 20.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: Thomas Monjalon --- I would prefer increasing the ABI version to 20.2 for an easy mapping with code version: DPDK 19.11 = ABI 20 libs 19.11 = .so.20.0 DPDK 20.02 = ABI 20 libs 20.02 = .so.20.2 DPDK 20.05 = ABI 20 libs 20.05 = .so.20.5 DPDK 20.08 = ABI 20 libs 20.08 = .so.20.8 Opinions? --- ABI_VERSION | 2 +- VERSION | 2 +- doc/guides/rel_notes/index.rst | 1 + doc/guides/rel_notes/release_20_02.rst | 139 +++++++++++++++++++++++++ 4 files changed, 142 insertions(+), 2 deletions(-) create mode 100644 doc/guides/rel_notes/release_20_02.rst diff --git a/ABI_VERSION b/ABI_VERSION index 9a7c1e503f..2e73f8d2aa 100644 --- a/ABI_VERSION +++ b/ABI_VERSION @@ -1 +1 @@ -20.0 +20.1 diff --git a/VERSION b/VERSION index 22131b00aa..7b50df9859 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -19.11.0 +20.02-rc0 diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst index 26f4a97cce..24d927d33e 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_02 release_19_11 release_19_08 release_19_05 diff --git a/doc/guides/rel_notes/release_20_02.rst b/doc/guides/rel_notes/release_20_02.rst new file mode 100644 index 0000000000..30605a3239 --- /dev/null +++ b/doc/guides/rel_notes/release_20_02.rst @@ -0,0 +1,139 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2019 The DPDK contributors + +.. include:: + +DPDK Release 20.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_20_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 change, kept ABI v20. DPDK 20.02 is compatible with DPDK 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. + ========================================================= -- 2.23.0