From: Luca Boccassi Date: Thu, 17 May 2018 13:53:35 +0000 (+0100) Subject: doc: advise to specify LTS branch when backporting patches X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=d53f61b6fec72e484e3d931b084d20f5a8891793;p=dpdk.git doc: advise to specify LTS branch when backporting patches We have many stable branches being maintained at the same time, and sometimes it's not clear which branch a patch is being backported for. Note in the guidelines that it should be specified via the cover letter, annotation or using --subject-prefix. Also note to send only to stable@dpdk.org, not dev@dpdk.org. Signed-off-by: Luca Boccassi Acked-by: Thomas Monjalon --- diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index 0275db93e0..7bb5710c8c 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -491,6 +491,20 @@ Experienced committers may send patches directly with ``git send-email`` without The options ``--annotate`` and ``confirm = always`` are recommended for checking patches before sending. +Backporting patches for Stable Releases +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Sometimes a maintainer or contributor wishes, or can be asked, to send a patch +for a stable release rather than mainline. +In this case the patch(es) should be sent to ``stable@dpdk.org``, +not to ``dev@dpdk.org``. + +Given that there are multiple stable releases being maintained at the same time, +please specify exactly which branch(es) the patch is for +using ``git send-email --subject-prefix='PATCH 16.11' ...`` +and also optionally in the cover letter or in the annotation. + + The Review Process ------------------