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_16_07.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.
41 This section should contain bug fixes added to the relevant sections. Sample format:
43 * **code/section Fixed issue in the past tense with a full stop.**
45 Add a short 1-2 sentence description of the resolved issue in the past tense.
46 The title should contain the code/lib section like a commit message.
47 Add the entries in alphabetic order in the relevant sections below.
73 This section should contain new known issues in this release. Sample format:
75 * **Add title in present tense with full stop.**
77 Add a short 1-2 sentence description of the known issue in the present
78 tense. Add information on any known workarounds.
84 This section should contain API changes. Sample format:
86 * Add a short 1-2 sentence description of the API change. Use fixed width
87 quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
89 * The following counters are removed from ``rte_eth_stats`` structure:
90 ibadcrc, ibadlen, imcasts, fdirmatch, fdirmiss,
91 tx_pause_xon, rx_pause_xon, tx_pause_xoff, rx_pause_xoff.
97 * Add a short 1-2 sentence description of the ABI change that was announced in
98 the previous releases and made in this release. Use fixed width quotes for
99 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
101 * The ``rte_port_source_params`` structure has new fields to support PCAP file.
102 It was already in release 16.04 with ``RTE_NEXT_ABI`` flag.
105 Shared Library Versions
106 -----------------------
108 Update any library version updated in this release and prepend with a ``+`` sign.
110 The libraries prepended with a plus sign were incremented in this version.
118 librte_distributor.so.1
146 This section should contain a list of platforms that were tested with this
160 This section should contain a list of NICs that were tested with this release.