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 =========================================================
45 * **Added powerpc support in pci probing for vfio-pci devices.**
47 sPAPR IOMMU based pci probing enabled for vfio-pci devices.
52 .. This section should contain bug fixes added to the relevant
53 sections. Sample format:
55 * **code/section Fixed issue in the past tense with a full stop.**
57 Add a short 1-2 sentence description of the resolved issue in the past
60 The title should contain the code/lib section like a commit message.
62 Add the entries in alphabetic order in the relevant sections below.
64 This section is a comment. do not overwrite or remove it.
65 Also, make sure to start the actual text at the margin.
66 =========================================================
92 .. This section should contain new known issues in this release. Sample format:
94 * **Add title in present tense with full stop.**
96 Add a short 1-2 sentence description of the known issue in the present
97 tense. Add information on any known workarounds.
99 This section is a comment. do not overwrite or remove it.
100 Also, make sure to start the actual text at the margin.
101 =========================================================
107 .. This section should contain API changes. Sample format:
109 * Add a short 1-2 sentence description of the API change. Use fixed width
110 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
113 This section is a comment. do not overwrite or remove it.
114 Also, make sure to start the actual text at the margin.
115 =========================================================
121 .. This section should contain ABI changes. Sample format:
123 * Add a short 1-2 sentence description of the ABI change that was announced
124 in the previous releases and made in this release. Use fixed width quotes
125 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
127 This section is a comment. do not overwrite or remove it.
128 Also, make sure to start the actual text at the margin.
129 =========================================================
135 .. This section should contain removed items in this release. Sample format:
137 * Add a short 1-2 sentence description of the removed item in the past
140 This section is a comment. do not overwrite or remove it.
141 Also, make sure to start the actual text at the margin.
142 =========================================================
144 * KNI vhost support removed.
147 Shared Library Versions
148 -----------------------
150 .. Update any library version updated in this release and prepend with a ``+``
154 + librte_cfgfile.so.2
157 This section is a comment. do not overwrite or remove it.
158 =========================================================
161 The libraries prepended with a plus sign were incremented in this version.
168 librte_cryptodev.so.2
169 librte_distributor.so.1
199 .. This section should contain a list of platforms that were tested with this
204 * <vendor> platform with <vendor> <type of devices> combinations
209 * Other relevant details...
211 This section is a comment. do not overwrite or remove it.
212 Also, make sure to start the actual text at the margin.
213 =========================================================