1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2019 The DPDK contributors
4 .. include:: <isonum.txt>
9 .. **Read this first.**
11 The text in the sections below explains how to update the release notes.
13 Use proper spelling, capitalization and punctuation in all sections.
15 Variable and config names should be quoted as fixed width text:
18 Build the docs and view the output file to ensure the changes are correct::
22 xdg-open build/doc/html/guides/rel_notes/release_20_02.html
28 .. This section should contain new features added in this release.
31 * **Add a title in the past tense with a full stop.**
33 Add a short 1-2 sentence description in the past tense.
34 The description should be enough to allow someone scanning
35 the release notes to understand the new feature.
37 If the feature adds a lot of sub-features you can use a bullet list
40 * Added feature foo to do something.
41 * Enhanced feature bar to do something else.
43 Refer to the previous release notes for examples.
45 Suggested order in release notes items:
46 * Core libs (EAL, mempool, ring, mbuf, buses)
47 * Device abstraction libs and PMDs
49 - cryptodev (lib, PMDs)
50 - eventdev (lib, PMDs)
53 * Apps, Examples, Tools (if significant)
55 This section is a comment. Do not overwrite or remove it.
56 Also, make sure to start the actual text at the margin.
57 =========================================================
59 * **Added Wait Until Equal API.**
61 A new API has been added to wait for a memory location to be updated with a
62 16-bit, 32-bit, 64-bit value.
68 .. This section should contain removed items in this release. Sample format:
70 * Add a short 1-2 sentence description of the removed item
73 This section is a comment. Do not overwrite or remove it.
74 Also, make sure to start the actual text at the margin.
75 =========================================================
81 .. This section should contain API changes. Sample format:
83 * sample: Add a short 1-2 sentence description of the API change
84 which was announced in the previous releases and made in this release.
85 Start with a scope label like "ethdev:".
86 Use fixed width quotes for ``function_names`` or ``struct_names``.
89 This section is a comment. Do not overwrite or remove it.
90 Also, make sure to start the actual text at the margin.
91 =========================================================
97 .. This section should contain ABI changes. Sample format:
99 * sample: Add a short 1-2 sentence description of the ABI change
100 which was announced in the previous releases and made in this release.
101 Start with a scope label like "ethdev:".
102 Use fixed width quotes for ``function_names`` or ``struct_names``.
105 This section is a comment. Do not overwrite or remove it.
106 Also, make sure to start the actual text at the margin.
107 =========================================================
109 * No change, kept ABI v20. DPDK 20.02 is compatible with DPDK 19.11.
115 .. This section should contain new known issues in this release. Sample format:
117 * **Add title in present tense with full stop.**
119 Add a short 1-2 sentence description of the known issue
120 in the present tense. Add information on any known workarounds.
122 This section is a comment. Do not overwrite or remove it.
123 Also, make sure to start the actual text at the margin.
124 =========================================================
130 .. This section should contain a list of platforms that were tested
135 * <vendor> platform with <vendor> <type of devices> combinations
140 * Other relevant details...
142 This section is a comment. Do not overwrite or remove it.
143 Also, make sure to start the actual text at the margin.
144 =========================================================