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_11.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 =========================================================
48 .. This section should contain bug fixes added to the relevant
49 sections. Sample format:
51 * **code/section Fixed issue in the past tense with a full stop.**
53 Add a short 1-2 sentence description of the resolved issue in the past
56 The title should contain the code/lib section like a commit message.
58 Add the entries in alphabetic order in the relevant sections below.
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 * **Service core fails to call service callback due to atomic lock**
70 In a specific configuration of multi-thread unsafe services and service
71 cores, a service core previously did not correctly release the atomic lock
72 on the service. This would result in the cores polling the service, but it
73 looked like another thread was executing the service callback. The logic for
74 atomic locking of the services has been fixed and refactored for readability.
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 =========================================================
124 .. This section should contain ABI changes. Sample format:
126 * Add a short 1-2 sentence description of the ABI change that was announced
127 in the previous releases and made in this release. Use fixed width quotes
128 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
130 This section is a comment. do not overwrite or remove it.
131 Also, make sure to start the actual text at the margin.
132 =========================================================
136 Shared Library Versions
137 -----------------------
139 .. Update any library version updated in this release and prepend with a ``+``
143 + librte_cfgfile.so.2
146 This section is a comment. do not overwrite or remove it.
147 =========================================================
150 The libraries prepended with a plus sign were incremented in this version.
155 librte_bitratestats.so.1
158 librte_cryptodev.so.3
159 librte_distributor.so.1
169 librte_latencystats.so.1
193 .. This section should contain a list of platforms that were tested with this
198 * <vendor> platform with <vendor> <type of devices> combinations
203 * Other relevant details...
205 This section is a comment. do not overwrite or remove it.
206 Also, make sure to start the actual text at the margin.
207 =========================================================