1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2021 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_21_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 (ordered alphabetically by vendor name)
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 =======================================================
58 * **Enabled new devargs parser.**
60 * Enabled devargs syntax
61 ``bus=X,paramX=x/class=Y,paramY=y/driver=Z,paramZ=z``
62 * Added bus-level parsing of the devargs syntax.
63 * Kept compatibility with the legacy syntax as parsing fallback.
65 * **Updated Marvell cnxk crypto PMD.**
67 * Added AES-CBC SHA1-HMAC support in lookaside protocol (IPsec) for CN10K.
73 .. This section should contain removed items in this release. Sample format:
75 * Add a short 1-2 sentence description of the removed item
78 This section is a comment. Do not overwrite or remove it.
79 Also, make sure to start the actual text at the margin.
80 =======================================================
86 .. This section should contain API changes. Sample format:
88 * sample: Add a short 1-2 sentence description of the API change
89 which was announced in the previous releases and made in this release.
90 Start with a scope label like "ethdev:".
91 Use fixed width quotes for ``function_names`` or ``struct_names``.
94 This section is a comment. Do not overwrite or remove it.
95 Also, make sure to start the actual text at the margin.
96 =======================================================
102 .. This section should contain ABI changes. Sample format:
104 * sample: Add a short 1-2 sentence description of the ABI change
105 which was announced in the previous releases and made in this release.
106 Start with a scope label like "ethdev:".
107 Use fixed width quotes for ``function_names`` or ``struct_names``.
110 This section is a comment. Do not overwrite or remove it.
111 Also, make sure to start the actual text at the margin.
112 =======================================================
118 .. This section should contain new known issues in this release. Sample format:
120 * **Add title in present tense with full stop.**
122 Add a short 1-2 sentence description of the known issue
123 in the present tense. Add information on any known workarounds.
125 This section is a comment. Do not overwrite or remove it.
126 Also, make sure to start the actual text at the margin.
127 =======================================================
133 .. This section should contain a list of platforms that were tested
138 * <vendor> platform with <vendor> <type of devices> combinations
143 * Other relevant details...
145 This section is a comment. Do not overwrite or remove it.
146 Also, make sure to start the actual text at the margin.
147 =======================================================