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_08.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 * **Added Generic Flow API support to enic.**
46 Flow API support for outer Ethernet, VLAN, IPv4, IPv6, UDP, TCP, SCTP, VxLAN
47 and inner Ethernet, VLAN, IPv4, IPv6, UDP and TCP pattern items with QUEUE,
48 MARK, FLAG and VOID actions for ingress traffic.
50 * **Added support for Chelsio T6 family of adapters**
52 CXGBE PMD updated to run Chelsio T6 family of adapters.
54 * **Added latency and performance improvements for cxgbe**
56 TX and RX path reworked to improve performance. Also reduced latency
63 .. This section should contain bug fixes added to the relevant
64 sections. Sample format:
66 * **code/section Fixed issue in the past tense with a full stop.**
68 Add a short 1-2 sentence description of the resolved issue in the past
71 The title should contain the code/lib section like a commit message.
73 Add the entries in alphabetic order in the relevant sections below.
75 This section is a comment. do not overwrite or remove it.
76 Also, make sure to start the actual text at the margin.
77 =========================================================
103 .. This section should contain new known issues in this release. Sample format:
105 * **Add title in present tense with full stop.**
107 Add a short 1-2 sentence description of the known issue in the present
108 tense. Add information on any known workarounds.
110 This section is a comment. do not overwrite or remove it.
111 Also, make sure to start the actual text at the margin.
112 =========================================================
118 .. This section should contain API changes. Sample format:
120 * Add a short 1-2 sentence description of the API change. Use fixed width
121 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past
124 This section is a comment. do not overwrite or remove it.
125 Also, make sure to start the actual text at the margin.
126 =========================================================
132 .. This section should contain ABI changes. Sample format:
134 * Add a short 1-2 sentence description of the ABI change that was announced
135 in the previous releases and made in this release. Use fixed width quotes
136 for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
138 This section is a comment. do not overwrite or remove it.
139 Also, make sure to start the actual text at the margin.
140 =========================================================
144 Shared Library Versions
145 -----------------------
147 .. Update any library version updated in this release and prepend with a ``+``
151 + librte_cfgfile.so.2
154 This section is a comment. do not overwrite or remove it.
155 =========================================================
158 The libraries prepended with a plus sign were incremented in this version.
163 librte_bitratestats.so.1
166 librte_cryptodev.so.2
167 librte_distributor.so.1
175 librte_latencystats.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 =========================================================