4 .. **Read this first.**
6 The text 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: ``LIKE_THIS``.
12 Build the docs and view the output file to ensure the changes are correct::
16 firefox build/doc/html/guides/rel_notes/release_17_02.html
22 .. This section should contain new features added in this release. Sample format:
24 * **Add a title in the past tense with a full stop.**
26 Add a short 1-2 sentence description in the past tense. The description
27 should be enough to allow someone scanning the release notes to understand
30 If the feature adds a lot of sub-features you can use a bullet list like this.
32 * Added feature foo to do something.
33 * Enhanced feature bar to do something else.
35 Refer to the previous release notes for examples.
37 This section is a comment. do not overwrite or remove it.
38 Also, make sure to start the actual text at the margin.
39 =========================================================
45 .. This section should contain bug fixes added to the relevant sections. Sample format:
47 * **code/section Fixed issue in the past tense with a full stop.**
49 Add a short 1-2 sentence description of the resolved issue in the past tense.
50 The title should contain the code/lib section like a commit message.
51 Add the entries in alphabetic order in the relevant sections below.
53 This section is a comment. do not overwrite or remove it.
54 Also, make sure to start the actual text at the margin.
55 =========================================================
81 .. This section should contain new known issues in this release. Sample format:
83 * **Add title in present tense with full stop.**
85 Add a short 1-2 sentence description of the known issue in the present
86 tense. Add information on any known workarounds.
88 This section is a comment. do not overwrite or remove it.
89 Also, make sure to start the actual text at the margin.
90 =========================================================
96 .. This section should contain API changes. Sample format:
98 * Add a short 1-2 sentence description of the API change. Use fixed width
99 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
101 This section is a comment. do not overwrite or remove it.
102 Also, make sure to start the actual text at the margin.
103 =========================================================
109 .. This section should contain ABI changes. Sample format:
111 * Add a short 1-2 sentence description of the ABI change that was announced in
112 the previous releases and made in this release. Use fixed width quotes for
113 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
115 This section is a comment. do not overwrite or remove it.
116 Also, make sure to start the actual text at the margin.
117 =========================================================
121 Shared Library Versions
122 -----------------------
124 .. Update any library version updated in this release and prepend with a ``+``
128 + librte_cfgfile.so.2
131 This section is a comment. do not overwrite or remove it.
132 =========================================================
135 The libraries prepended with a plus sign were incremented in this version.
142 librte_cryptodev.so.2
143 librte_distributor.so.1
173 .. This section should contain a list of platforms that were tested with this release.
182 This section is a comment. do not overwrite or remove it.
183 Also, make sure to start the actual text at the margin.
184 =========================================================
190 .. This section should contain a list of NICs that were tested with this release.
199 This section is a comment. do not overwrite or remove it.
200 Also, make sure to start the actual text at the margin.
201 =========================================================
207 .. This section should contain a list of OSes that were tested with this release.
208 The format is as follows, in alphabetical order:
214 * Red Hat Enterprise Linux 7.2
215 * SUSE Enterprise Linux 12
220 This section is a comment. do not overwrite or remove it.
221 Also, make sure to start the actual text at the margin.
222 =========================================================