get:
Show a patch.

patch:
Update a patch.

put:
Update a patch.

GET /api/patches/88013/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 88013,
    "url": "http://patches.dpdk.org/api/patches/88013/?format=api",
    "web_url": "http://patches.dpdk.org/project/dpdk/patch/20210219111711.416979-1-ktraynor@redhat.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": "<20210219111711.416979-1-ktraynor@redhat.com>",
    "list_archive_url": "https://inbox.dpdk.org/dev/20210219111711.416979-1-ktraynor@redhat.com",
    "date": "2021-02-19T11:17:11",
    "name": "[v2] doc: update stable section",
    "commit_ref": null,
    "pull_url": null,
    "state": "accepted",
    "archived": true,
    "hash": "62cd15d4f92f011590f548118b84c2a3d8d50319",
    "submitter": {
        "id": 598,
        "url": "http://patches.dpdk.org/api/people/598/?format=api",
        "name": "Kevin Traynor",
        "email": "ktraynor@redhat.com"
    },
    "delegate": {
        "id": 1,
        "url": "http://patches.dpdk.org/api/users/1/?format=api",
        "username": "tmonjalo",
        "first_name": "Thomas",
        "last_name": "Monjalon",
        "email": "thomas@monjalon.net"
    },
    "mbox": "http://patches.dpdk.org/project/dpdk/patch/20210219111711.416979-1-ktraynor@redhat.com/mbox/",
    "series": [
        {
            "id": 15304,
            "url": "http://patches.dpdk.org/api/series/15304/?format=api",
            "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=15304",
            "date": "2021-02-19T11:17:11",
            "name": "[v2] doc: update stable section",
            "version": 2,
            "mbox": "http://patches.dpdk.org/series/15304/mbox/"
        }
    ],
    "comments": "http://patches.dpdk.org/api/patches/88013/comments/",
    "check": "fail",
    "checks": "http://patches.dpdk.org/api/patches/88013/checks/",
    "tags": {},
    "related": [],
    "headers": {
        "Return-Path": "<dev-bounces@dpdk.org>",
        "X-Original-To": "patchwork@inbox.dpdk.org",
        "Delivered-To": "patchwork@inbox.dpdk.org",
        "Received": [
            "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id BD3C7A055D;\n\tFri, 19 Feb 2021 12:17:54 +0100 (CET)",
            "from [217.70.189.124] (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 3AE7116090A;\n\tFri, 19 Feb 2021 12:17:38 +0100 (CET)",
            "from us-smtp-delivery-124.mimecast.com\n (us-smtp-delivery-124.mimecast.com [63.128.21.124])\n by mails.dpdk.org (Postfix) with ESMTP id E4DDC16090A\n for <dev@dpdk.org>; Fri, 19 Feb 2021 12:17:36 +0100 (CET)",
            "from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com\n [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id\n us-mta-226-20qgx7n6O8O7MOOKR2hFOw-1; Fri, 19 Feb 2021 06:17:33 -0500",
            "from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com\n [10.5.11.22])\n (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))\n (No client certificate requested)\n by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 94122CE647;\n Fri, 19 Feb 2021 11:17:31 +0000 (UTC)",
            "from rh.redhat.com (ovpn-112-169.ams2.redhat.com [10.36.112.169])\n by smtp.corp.redhat.com (Postfix) with ESMTP id DB916100164C;\n Fri, 19 Feb 2021 11:17:29 +0000 (UTC)"
        ],
        "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1613733456;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n content-transfer-encoding:content-transfer-encoding;\n bh=EmSWmhXf135jPaaVtNouQig20EhGfEV8XrqHrj26Fjs=;\n b=Nt+M+/FXW9HmoLAYJly6A3vjdfhuERrBMYGnQJLcvhuFlZfdsDFjokNpZipHp0Zfo7crhJ\n RD1GrBvVaUMGaaAVoWWHHTBI482fNTnBAnTjw2n9mbxYYSNPTojjnxlojbrMe+e3zitLoX\n AxZC7KN34B6r5DeqcznLMSfG5Far8sg=",
        "X-MC-Unique": "20qgx7n6O8O7MOOKR2hFOw-1",
        "From": "Kevin Traynor <ktraynor@redhat.com>",
        "To": "dev@dpdk.org",
        "Cc": "stable@dpdk.org, bluca@debian.org, christian.ehrhardt@canonical.com,\n Kevin Traynor <ktraynor@redhat.com>",
        "Date": "Fri, 19 Feb 2021 11:17:11 +0000",
        "Message-Id": "<20210219111711.416979-1-ktraynor@redhat.com>",
        "MIME-Version": "1.0",
        "X-Scanned-By": "MIMEDefang 2.84 on 10.5.11.22",
        "Authentication-Results": "relay.mimecast.com;\n auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com",
        "X-Mimecast-Spam-Score": "0",
        "X-Mimecast-Originator": "redhat.com",
        "Content-Transfer-Encoding": "8bit",
        "Content-Type": "text/plain; charset=\"US-ASCII\"",
        "Subject": "[dpdk-dev] [PATCH v2] doc: update stable section",
        "X-BeenThere": "dev@dpdk.org",
        "X-Mailman-Version": "2.1.29",
        "Precedence": "list",
        "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
        "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>",
        "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
        "List-Post": "<mailto:dev@dpdk.org>",
        "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
        "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>",
        "Errors-To": "dev-bounces@dpdk.org",
        "Sender": "\"dev\" <dev-bounces@dpdk.org>"
    },
    "content": "Updating the docs to elaborate on the stable release\ncharacteristics and better document the current practice\nabout new features in stable releases.\n\nSigned-off-by: Kevin Traynor <ktraynor@redhat.com>\n\n---\nv2: Send to right dev list this time.  Fix typo.\n---\n doc/guides/contributing/stable.rst | 33 ++++++++++++++++++++++++------\n 1 file changed, 27 insertions(+), 6 deletions(-)",
    "diff": "diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst\nindex 20b081670..7a0a505aa 100644\n--- a/doc/guides/contributing/stable.rst\n+++ b/doc/guides/contributing/stable.rst\n@@ -19,4 +19,8 @@ consumers of DPDK with a stable target on which to base applications or\n packages.\n \n+The primary characteristics of stable releases is that they attempt to\n+fix issues and not introduce any new regressions while keeping backwards\n+compatibility with the initial release of the stable version.\n+\n The Long Term Support release (LTS) is a designation applied to a Stable\n Release to indicate longer term support.\n@@ -94,12 +98,29 @@ commit message body as follows::\n Fixes not suitable for backport should not include the ``Cc: stable@dpdk.org`` tag.\n \n-Features should not be backported to stable releases. It may be acceptable, in\n-limited cases, to back port features for the LTS release where:\n+To support the goal of stability and not introducing regressions, new code\n+being introduced is limited to bug fixes. New features should not be backported\n+to stable releases.\n \n-* There is a justifiable use case (for example a new PMD).\n-* The change is non-invasive.\n-* The work of preparing the backport is done by the proposer.\n-* There is support within the community.\n+In some limited cases, it may be acceptable to backport a new feature\n+to a stable release. Some of the factors which impact the decision by\n+stable maintainers are as follows:\n \n+* Does the feature break API/ABI?\n+* Does the feature break backwards compatibility?\n+* Is it for the latest LTS release (to avoid LTS upgrade issues)?\n+* Is there a commitment from the proposer or affiliation to validate the feature and check for regressions in related functionality?\n+* Is there a track record of the proposer or affiliation validating stable releases?\n+* Is it obvious that the feature will not impact existing functionality?\n+* How intrusive is the code change?\n+* What is the scope of the code change?\n+* Does it impact common components or vendor specific?\n+* Is there a justifiable use case (a clear user need)?\n+* Is there a community consensus about the backport?\n+\n+Performance improvements are generally not considered to be fixes, but may be considered\n+in some cases where:\n+\n+* It is fixing a performance regression that occurred previously.\n+* An existing feature in LTS is not usable as intended without it.\n \n The Stable Mailing List\n",
    "prefixes": [
        "v2"
    ]
}