Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/27494/?format=api
{ "id": 27494, "url": "http://patches.dpdk.org/api/patches/27494/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/1502266933-26883-1-git-send-email-john.mcnamara@intel.com/", "project": { "id": 1, "url": "http://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<1502266933-26883-1-git-send-email-john.mcnamara@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/1502266933-26883-1-git-send-email-john.mcnamara@intel.com", "date": "2017-08-09T08:22:13", "name": "[dpdk-dev,v2] doc: add template release notes for 17.11", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": true, "hash": "eb58121cad6d65df59b9e476bdddbe1158ac1079", "submitter": { "id": 154, "url": "http://patches.dpdk.org/api/people/154/?format=api", "name": "John McNamara", "email": "john.mcnamara@intel.com" }, "delegate": null, "mbox": "http://patches.dpdk.org/project/dpdk/patch/1502266933-26883-1-git-send-email-john.mcnamara@intel.com/mbox/", "series": [], "comments": "http://patches.dpdk.org/api/patches/27494/comments/", "check": "success", "checks": "http://patches.dpdk.org/api/patches/27494/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@dpdk.org", "Delivered-To": "patchwork@dpdk.org", "Received": [ "from [92.243.14.124] (localhost [IPv6:::1])\n\tby dpdk.org (Postfix) with ESMTP id 4CFB22B88;\n\tWed, 9 Aug 2017 10:22:30 +0200 (CEST)", "from mga05.intel.com (mga05.intel.com [192.55.52.43])\n\tby dpdk.org (Postfix) with ESMTP id B51CD2A5D\n\tfor <dev@dpdk.org>; Wed, 9 Aug 2017 10:22:28 +0200 (CEST)", "from orsmga002.jf.intel.com ([10.7.209.21])\n\tby fmsmga105.fm.intel.com with ESMTP; 09 Aug 2017 01:22:27 -0700", "from sivswdev02.ir.intel.com (HELO localhost.localdomain)\n\t([10.237.217.46])\n\tby orsmga002.jf.intel.com with ESMTP; 09 Aug 2017 01:22:26 -0700" ], "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.41,346,1498546800\"; d=\"scan'208\";a=\"121579910\"", "From": "John McNamara <john.mcnamara@intel.com>", "To": "dev@dpdk.org", "Cc": "John McNamara <john.mcnamara@intel.com>", "Date": "Wed, 9 Aug 2017 09:22:13 +0100", "Message-Id": "<1502266933-26883-1-git-send-email-john.mcnamara@intel.com>", "X-Mailer": "git-send-email 1.7.0.7", "In-Reply-To": "<1502195467-24712-1-git-send-email-john.mcnamara@intel.com>", "References": "<1502195467-24712-1-git-send-email-john.mcnamara@intel.com>", "Subject": "[dpdk-dev] [PATCH v2] doc: add template release notes for 17.11", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<http://dpdk.org/ml/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://dpdk.org/ml/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<http://dpdk.org/ml/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "Add template release notes for DPDK 17.11 with inline\ncomments and explanations of the various sections.\n\nSigned-off-by: John McNamara <john.mcnamara@intel.com>\n---\n\nV2: Updated library version numbers.\n\n\n doc/guides/rel_notes/index.rst | 1 +\n doc/guides/rel_notes/release_17_11.rst | 200 +++++++++++++++++++++++++++++++++\n 2 files changed, 201 insertions(+)\n create mode 100644 doc/guides/rel_notes/release_17_11.rst", "diff": "diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst\nindex b3c8090..35659d8 100644\n--- a/doc/guides/rel_notes/index.rst\n+++ b/doc/guides/rel_notes/index.rst\n@@ -36,6 +36,7 @@ Release Notes\n :numbered:\n \n rel_description\n+ release_17_11\n release_17_08\n release_17_05\n release_17_02\ndiff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst\nnew file mode 100644\nindex 0000000..170f4f9\n--- /dev/null\n+++ b/doc/guides/rel_notes/release_17_11.rst\n@@ -0,0 +1,200 @@\n+DPDK Release 17.11\n+==================\n+\n+.. **Read this first.**\n+\n+ The text in the sections below explains how to update the release notes.\n+\n+ Use proper spelling, capitalization and punctuation in all sections.\n+\n+ Variable and config names should be quoted as fixed width text:\n+ ``LIKE_THIS``.\n+\n+ Build the docs and view the output file to ensure the changes are correct::\n+\n+ make doc-guides-html\n+\n+ xdg-open build/doc/html/guides/rel_notes/release_17_11.html\n+\n+\n+New Features\n+------------\n+\n+.. This section should contain new features added in this release. Sample\n+ format:\n+\n+ * **Add a title in the past tense with a full stop.**\n+\n+ Add a short 1-2 sentence description in the past tense. The description\n+ should be enough to allow someone scanning the release notes to\n+ understand the new feature.\n+\n+ If the feature adds a lot of sub-features you can use a bullet list like\n+ this:\n+\n+ * Added feature foo to do something.\n+ * Enhanced feature bar to do something else.\n+\n+ Refer to the previous release notes for examples.\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n+\n+\n+Resolved Issues\n+---------------\n+\n+.. This section should contain bug fixes added to the relevant\n+ sections. Sample format:\n+\n+ * **code/section Fixed issue in the past tense with a full stop.**\n+\n+ Add a short 1-2 sentence description of the resolved issue in the past\n+ tense.\n+\n+ The title should contain the code/lib section like a commit message.\n+\n+ Add the entries in alphabetic order in the relevant sections below.\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n+\n+\n+EAL\n+~~~\n+\n+\n+Drivers\n+~~~~~~~\n+\n+\n+Libraries\n+~~~~~~~~~\n+\n+\n+Examples\n+~~~~~~~~\n+\n+\n+Other\n+~~~~~\n+\n+\n+Known Issues\n+------------\n+\n+.. This section should contain new known issues in this release. Sample format:\n+\n+ * **Add title in present tense with full stop.**\n+\n+ Add a short 1-2 sentence description of the known issue in the present\n+ tense. Add information on any known workarounds.\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n+\n+\n+API Changes\n+-----------\n+\n+.. This section should contain API changes. Sample format:\n+\n+ * Add a short 1-2 sentence description of the API change. Use fixed width\n+ quotes for ``rte_function_names`` or ``rte_struct_names``. Use the past\n+ tense.\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n+\n+\n+ABI Changes\n+-----------\n+\n+.. This section should contain ABI changes. Sample format:\n+\n+ * Add a short 1-2 sentence description of the ABI change that was announced\n+ in the previous releases and made in this release. Use fixed width quotes\n+ for ``rte_function_names`` or ``rte_struct_names``. Use the past tense.\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n+\n+\n+\n+Shared Library Versions\n+-----------------------\n+\n+.. Update any library version updated in this release and prepend with a ``+``\n+ sign, like this:\n+\n+ librte_acl.so.2\n+ + librte_cfgfile.so.2\n+ librte_cmdline.so.2\n+\n+ This section is a comment. do not overwrite or remove it.\n+ =========================================================\n+\n+\n+The libraries prepended with a plus sign were incremented in this version.\n+\n+.. code-block:: diff\n+\n+ librte_acl.so.2\n+ librte_bitratestats.so.1\n+ librte_cfgfile.so.2\n+ librte_cmdline.so.2\n+ librte_cryptodev.so.3\n+ librte_distributor.so.1\n+ librte_eal.so.5\n+ librte_ethdev.so.7\n+ librte_eventdev.so.2\n+ librte_gro.so.1\n+ librte_hash.so.2\n+ librte_ip_frag.so.1\n+ librte_jobstats.so.1\n+ librte_kni.so.2\n+ librte_kvargs.so.1\n+ librte_latencystats.so.1\n+ librte_lpm.so.2\n+ librte_mbuf.so.3\n+ librte_mempool.so.2\n+ librte_meter.so.1\n+ librte_metrics.so.1\n+ librte_net.so.1\n+ librte_pdump.so.1\n+ librte_pipeline.so.3\n+ librte_pmd_bond.so.1\n+ librte_pmd_ring.so.2\n+ librte_port.so.3\n+ librte_power.so.1\n+ librte_reorder.so.1\n+ librte_ring.so.1\n+ librte_sched.so.1\n+ librte_table.so.2\n+ librte_timer.so.1\n+ librte_vhost.so.3\n+\n+\n+Tested Platforms\n+----------------\n+\n+.. This section should contain a list of platforms that were tested with this\n+ release.\n+\n+ The format is:\n+\n+ * <vendor> platform with <vendor> <type of devices> combinations\n+\n+ * List of CPU\n+ * List of OS\n+ * List of devices\n+ * Other relevant details...\n+\n+ This section is a comment. do not overwrite or remove it.\n+ Also, make sure to start the actual text at the margin.\n+ =========================================================\n", "prefixes": [ "dpdk-dev", "v2" ] }