1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2018 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_02.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 enic driver.**
59 * Added support for ``RTE_ETH_DEV_CLOSE_REMOVE`` flag.
65 .. This section should contain removed items in this release. Sample format:
67 * Add a short 1-2 sentence description of the removed item
70 This section is a comment. Do not overwrite or remove it.
71 Also, make sure to start the actual text at the margin.
72 =========================================================
78 .. This section should contain API changes. Sample format:
80 * sample: Add a short 1-2 sentence description of the API change
81 which was announced in the previous releases and made in this release.
82 Start with a scope label like "ethdev:".
83 Use fixed width quotes for ``function_names`` or ``struct_names``.
86 This section is a comment. Do not overwrite or remove it.
87 Also, make sure to start the actual text at the margin.
88 =========================================================
94 .. This section should contain ABI changes. Sample format:
96 * sample: Add a short 1-2 sentence description of the ABI change
97 which was announced in the previous releases and made in this release.
98 Start with a scope label like "ethdev:".
99 Use fixed width quotes for ``function_names`` or ``struct_names``.
102 This section is a comment. Do not overwrite or remove it.
103 Also, make sure to start the actual text at the margin.
104 =========================================================
107 Shared Library Versions
108 -----------------------
110 .. Update any library version updated in this release
111 and prepend with a ``+`` sign, like this:
117 This section is a comment. Do not overwrite or remove it.
118 =========================================================
120 The libraries prepended with a plus sign were incremented in this version.
126 librte_bitratestats.so.2
129 librte_bus_fslmc.so.2
130 librte_bus_ifpga.so.2
133 librte_bus_vmbus.so.2
136 librte_compressdev.so.1
137 librte_cryptodev.so.5
138 librte_distributor.so.1
143 librte_flow_classify.so.1
151 librte_latencystats.so.1
165 librte_pmd_ixgbe.so.2
166 librte_pmd_dpaa2_qdma.so.1
168 librte_pmd_softnic.so.1
169 librte_pmd_vhost.so.2
185 .. This section should contain new known issues in this release. Sample format:
187 * **Add title in present tense with full stop.**
189 Add a short 1-2 sentence description of the known issue
190 in the present tense. Add information on any known workarounds.
192 This section is a comment. Do not overwrite or remove it.
193 Also, make sure to start the actual text at the margin.
194 =========================================================
200 .. This section should contain a list of platforms that were tested
205 * <vendor> platform with <vendor> <type of devices> combinations
210 * Other relevant details...
212 This section is a comment. Do not overwrite or remove it.
213 Also, make sure to start the actual text at the margin.
214 =========================================================