1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2020 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::
21 xdg-open build/doc/html/guides/rel_notes/release_20_11.html
27 .. This section should contain new features added in this release.
30 * **Add a title in the past tense with a full stop.**
32 Add a short 1-2 sentence description in the past tense.
33 The description should be enough to allow someone scanning
34 the release notes to understand the new feature.
36 If the feature adds a lot of sub-features you can use a bullet list
39 * Added feature foo to do something.
40 * Enhanced feature bar to do something else.
42 Refer to the previous release notes for examples.
44 Suggested order in release notes items:
45 * Core libs (EAL, mempool, ring, mbuf, buses)
46 * Device abstraction libs and PMDs
48 - cryptodev (lib, PMDs)
49 - eventdev (lib, PMDs)
52 * Apps, Examples, Tools (if significant)
54 This section is a comment. Do not overwrite or remove it.
55 Also, make sure to start the actual text at the margin.
56 =======================================================
62 .. This section should contain removed items in this release. Sample format:
64 * Add a short 1-2 sentence description of the removed item
67 This section is a comment. Do not overwrite or remove it.
68 Also, make sure to start the actual text at the margin.
69 =======================================================
75 .. This section should contain API changes. Sample format:
77 * sample: Add a short 1-2 sentence description of the API change
78 which was announced in the previous releases and made in this release.
79 Start with a scope label like "ethdev:".
80 Use fixed width quotes for ``function_names`` or ``struct_names``.
83 This section is a comment. Do not overwrite or remove it.
84 Also, make sure to start the actual text at the margin.
85 =======================================================
87 * eal: The ``rte_logs`` struct and global symbol was made private
88 and is no longer part of the API.
90 * mem: Removed the unioned field ``phys_addr`` from
91 the structures ``rte_memseg`` and ``rte_memzone``.
92 The field ``iova`` is remaining from the old unions.
94 * mbuf: Removed the unioned field ``refcnt_atomic`` from
95 the structures ``rte_mbuf`` and ``rte_mbuf_ext_shared_info``.
96 The field ``refcnt`` is remaining from the old unions.
98 * rawdev: Added a structure size parameter to the functions
99 ``rte_rawdev_queue_setup()``, ``rte_rawdev_queue_conf_get()``,
100 ``rte_rawdev_info_get()`` and ``rte_rawdev_configure()``,
101 allowing limited driver type-checking and ABI compatibility.
103 * rawdev: Changed the return type of the function ``rte_dev_info_get()``
104 and the function ``rte_rawdev_queue_conf_get()``
105 from ``void`` to ``int`` allowing the return of error codes from drivers.
107 * bpf: ``RTE_BPF_XTYPE_NUM`` has been dropped from ``rte_bpf_xtype``.
113 .. This section should contain ABI changes. Sample format:
115 * sample: Add a short 1-2 sentence description of the ABI change
116 which was announced in the previous releases and made in this release.
117 Start with a scope label like "ethdev:".
118 Use fixed width quotes for ``function_names`` or ``struct_names``.
121 This section is a comment. Do not overwrite or remove it.
122 Also, make sure to start the actual text at the margin.
123 =======================================================
129 .. This section should contain new known issues in this release. Sample format:
131 * **Add title in present tense with full stop.**
133 Add a short 1-2 sentence description of the known issue
134 in the present tense. Add information on any known workarounds.
136 This section is a comment. Do not overwrite or remove it.
137 Also, make sure to start the actual text at the margin.
138 =======================================================
144 .. This section should contain a list of platforms that were tested
149 * <vendor> platform with <vendor> <type of devices> combinations
154 * Other relevant details...
156 This section is a comment. Do not overwrite or remove it.
157 Also, make sure to start the actual text at the margin.
158 =======================================================