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_17_05.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 * **Increased number of next hops for LPM IPv6 to 2^21.**
46 The next_hop field is extended from 8 bits to 21 bits for IPv6.
48 * **Added powerpc support in pci probing for vfio-pci devices.**
50 sPAPR IOMMU based pci probing enabled for vfio-pci devices.
55 .. This section should contain bug fixes added to the relevant
56 sections. Sample format:
58 * **code/section Fixed issue in the past tense with a full stop.**
60 Add a short 1-2 sentence description of the resolved issue in the past
63 The title should contain the code/lib section like a commit message.
65 Add the entries in alphabetic order in the relevant sections below.
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 =========================================================
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 =========================================================
110 .. This section should contain API changes. Sample format:
112 * Add a short 1-2 sentence description of the API change. Use fixed width
113 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
116 This section is a comment. do not overwrite or remove it.
117 Also, make sure to start the actual text at the margin.
118 =========================================================
120 * The LPM ``next_hop`` field is extended from 8 bits to 21 bits for IPv6
121 while keeping ABI compatibility.
126 .. This section should contain ABI changes. Sample format:
128 * Add a short 1-2 sentence description of the ABI change that was announced
129 in the previous releases and made in this release. Use fixed width quotes
130 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
132 This section is a comment. do not overwrite or remove it.
133 Also, make sure to start the actual text at the margin.
134 =========================================================
140 .. This section should contain removed items in this release. Sample format:
142 * Add a short 1-2 sentence description of the removed item in the past
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 =========================================================
149 * KNI vhost support removed.
152 Shared Library Versions
153 -----------------------
155 .. Update any library version updated in this release and prepend with a ``+``
159 + librte_cfgfile.so.2
162 This section is a comment. do not overwrite or remove it.
163 =========================================================
166 The libraries prepended with a plus sign were incremented in this version.
173 librte_cryptodev.so.2
174 librte_distributor.so.1
204 .. This section should contain a list of platforms that were tested with this
209 * <vendor> platform with <vendor> <type of devices> combinations
214 * Other relevant details...
216 This section is a comment. do not overwrite or remove it.
217 Also, make sure to start the actual text at the margin.
218 =========================================================