4 .. **Read this first.**
6 The text in the sections below explains how to update the release notes.
8 Use proper spelling, capitalization and punctuation in all sections.
10 Variable and config names should be quoted as fixed width text:
13 Build the docs and view the output file to ensure the changes are correct::
17 xdg-open build/doc/html/guides/rel_notes/release_18_02.html
23 .. This section should contain new features added in this release. Sample
26 * **Add a title in the past tense with a full stop.**
28 Add a short 1-2 sentence description in the past tense. The description
29 should be enough to allow someone scanning the release notes to
30 understand the new feature.
32 If the feature adds a lot of sub-features you can use a bullet list like
35 * Added feature foo to do something.
36 * Enhanced feature bar to do something else.
38 Refer to the previous release notes for examples.
40 This section is a comment. do not overwrite or remove it.
41 Also, make sure to start the actual text at the margin.
42 =========================================================
44 * **Add MAC loopback support for i40e.**
46 Add MAC loopback support for i40e in order to support test task asked by
47 users. According to the device configuration, it will setup TX->RX loopback
54 .. This section should contain API changes. Sample format:
56 * Add a short 1-2 sentence description of the API change. Use fixed width
57 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
60 This section is a comment. do not overwrite or remove it.
61 Also, make sure to start the actual text at the margin.
62 =========================================================
68 .. This section should contain ABI changes. Sample format:
70 * Add a short 1-2 sentence description of the ABI change that was announced
71 in the previous releases and made in this release. Use fixed width quotes
72 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
74 This section is a comment. do not overwrite or remove it.
75 Also, make sure to start the actual text at the margin.
76 =========================================================
82 .. This section should contain removed items in this release. Sample format:
84 * Add a short 1-2 sentence description of the removed item in the past
87 This section is a comment. do not overwrite or remove it.
88 Also, make sure to start the actual text at the margin.
89 =========================================================
95 .. This section should contain new known issues in this release. Sample format:
97 * **Add title in present tense with full stop.**
99 Add a short 1-2 sentence description of the known issue in the present
100 tense. Add information on any known workarounds.
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 and prepend with a ``+``
114 + librte_cfgfile.so.2
117 This section is a comment. do not overwrite or remove it.
118 =========================================================
121 The libraries prepended with a plus sign were incremented in this version.
126 librte_bitratestats.so.2
128 librte_bus_fslmc.so.1
133 librte_cryptodev.so.4
134 librte_distributor.so.1
138 librte_flow_classify.so.1
146 librte_latencystats.so.1
159 librte_pmd_ixgbe.so.2
161 librte_pmd_softnic.so.1
162 librte_pmd_vhost.so.2
178 .. This section should contain a list of platforms that were tested with this
183 * <vendor> platform with <vendor> <type of devices> combinations
188 * Other relevant details...
190 This section is a comment. do not overwrite or remove it.
191 Also, make sure to start the actual text at the margin.
192 =========================================================