1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2019 The DPDK contributors
7 .. **Read this first.**
9 The text in the sections below explains how to update the release notes.
11 Use proper spelling, capitalization and punctuation in all sections.
13 Variable and config names should be quoted as fixed width text:
16 Build the docs and view the output file to ensure the changes are correct::
20 xdg-open build/doc/html/guides/rel_notes/release_19_08.html
26 .. This section should contain new features added in this release.
29 * **Add a title in the past tense with a full stop.**
31 Add a short 1-2 sentence description in the past tense.
32 The description should be enough to allow someone scanning
33 the release notes to understand the new feature.
35 If the feature adds a lot of sub-features you can use a bullet list
38 * Added feature foo to do something.
39 * Enhanced feature bar to do something else.
41 Refer to the previous release notes for examples.
43 Suggested order in release notes items:
44 * Core libs (EAL, mempool, ring, mbuf, buses)
45 * Device abstraction libs and PMDs
47 - cryptodev (lib, PMDs)
48 - eventdev (lib, PMDs)
51 * Apps, Examples, Tools (if significant)
53 This section is a comment. Do not overwrite or remove it.
54 Also, make sure to start the actual text at the margin.
55 =========================================================
57 * **Updated the bnxt PMD.**
59 Updated the bnxt PMD. The major enhancements include:
61 * Performance optimizations in non-vector Tx path
67 .. This section should contain removed items in this release. Sample format:
69 * Add a short 1-2 sentence description of the removed item
72 This section is a comment. Do not overwrite or remove it.
73 Also, make sure to start the actual text at the margin.
74 =========================================================
76 * Removed KNI ethtool, CONFIG_RTE_KNI_KMOD_ETHTOOL, support.
78 * build: armv8 crypto extension is disabled.
84 .. This section should contain API changes. Sample format:
86 * sample: Add a short 1-2 sentence description of the API change
87 which was announced in the previous releases and made in this release.
88 Start with a scope label like "ethdev:".
89 Use fixed width quotes for ``function_names`` or ``struct_names``.
92 This section is a comment. Do not overwrite or remove it.
93 Also, make sure to start the actual text at the margin.
94 =========================================================
96 * The network structures, definitions and functions have
97 been prefixed by ``rte_`` to resolve conflicts with libc headers.
103 .. This section should contain ABI changes. Sample format:
105 * sample: Add a short 1-2 sentence description of the ABI change
106 which was announced in the previous releases and made in this release.
107 Start with a scope label like "ethdev:".
108 Use fixed width quotes for ``function_names`` or ``struct_names``.
111 This section is a comment. Do not overwrite or remove it.
112 Also, make sure to start the actual text at the margin.
113 =========================================================
116 Shared Library Versions
117 -----------------------
119 .. Update any library version updated in this release
120 and prepend with a ``+`` sign, like this:
126 This section is a comment. Do not overwrite or remove it.
127 =========================================================
129 The libraries prepended with a plus sign were incremented in this version.
135 librte_bitratestats.so.2
138 librte_bus_fslmc.so.2
139 librte_bus_ifpga.so.2
142 librte_bus_vmbus.so.2
145 librte_compressdev.so.1
146 librte_cryptodev.so.7
147 librte_distributor.so.1
152 librte_flow_classify.so.1
161 librte_latencystats.so.1
175 librte_pmd_ixgbe.so.2
176 librte_pmd_dpaa2_qdma.so.1
178 librte_pmd_softnic.so.1
179 librte_pmd_vhost.so.2
197 .. This section should contain new known issues in this release. Sample format:
199 * **Add title in present tense with full stop.**
201 Add a short 1-2 sentence description of the known issue
202 in the present tense. Add information on any known workarounds.
204 This section is a comment. Do not overwrite or remove it.
205 Also, make sure to start the actual text at the margin.
206 =========================================================
212 .. This section should contain a list of platforms that were tested
217 * <vendor> platform with <vendor> <type of devices> combinations
222 * Other relevant details...
224 This section is a comment. Do not overwrite or remove it.
225 Also, make sure to start the actual text at the margin.
226 =========================================================