7 The text below explains how to update the release notes.
9 Use proper spelling, capitalization and punctuation in all sections.
11 Variable and config names should be quoted as fixed width text: ``LIKE_THIS``.
13 Build the docs and view the output file to ensure the changes are correct::
17 firefox build/doc/html/guides/rel_notes/release_16_04.html
23 This section should contain new features added in this release. Sample format:
25 * **Add a title in the past tense with a full stop.**
27 Add a short 1-2 sentence description in the past tense. The description
28 should be enough to allow someone scanning the release notes to understand
31 If the feature adds a lot of sub-features you can use a bullet list like this.
33 * Added feature foo to do something.
34 * Enhanced feature bar to do something else.
36 Refer to the previous release notes for examples.
40 Enabled virtio 1.0 support for virtio pmd driver.
42 * **Supported virtio offload in vhost-user.**
44 Add the offload and negotiation of checksum and TSO between vhost-user and
45 vanilla Linux virtio guest.
47 * **Added vhost-user live migration support.**
53 This section should contain bug fixes added to the relevant 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 tense.
58 The title should contain the code/lib section like a commit message.
59 Add the entries in alphabetic order in the relevant sections below.
85 This section should contain new known issues in this release. Sample format:
87 * **Add title in present tense with full stop.**
89 Add a short 1-2 sentence description of the known issue in the present
90 tense. Add information on any known workarounds.
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.
105 * Add a short 1-2 sentence description of the ABI change that was announced in
106 the previous releases and made in this release. Use fixed width quotes for
107 ``rte_function_names`` or ``rte_struct_names``. Use the past tense.
110 Shared Library Versions
111 -----------------------
113 Update any library version updated in this release and prepend with a ``+`` sign.
115 The libraries prepended with a plus sign were incremented in this version.
123 librte_distributor.so.1