[dpdk-dev] [PATCH v1 2/2] doc: add guidelines for stable tags
Hemant Agrawal
hemant.agrawal at nxp.com
Wed Jan 10 13:34:25 CET 2018
On 1/9/2018 9:21 PM, Marko Kovacevic wrote:
> Added contribution guideline for adding stable
> tags when sending patches all fix patches to the
> master branch that are candidates for backporting
>
> Signed-off-by: Marko Kovacevic <marko.kovacevic at intel.com>
> ---
> doc/guides/contributing/patches.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
> index e6b6e80..f98e601 100644
> --- a/doc/guides/contributing/patches.rst
> +++ b/doc/guides/contributing/patches.rst
> @@ -276,6 +276,21 @@ Coverity issue tag should be inserted into the commit message body as so::
>
> Signed-off-by: Alex Smith <alex.smith at example.com>
>
> +Patch for Stable Releases:
> +~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +All fix patches to the master branch that are candidates for backporting
> +should also be CCed to the `stable at dpdk.org <http://dpdk.org/ml/listinfo/stable>`_
> +mailing list. In the commit message body the Cc: stable at dpdk.org should be inserted as so::
> +
> + doc: fix some parameter description
> +
> + Update the docs, fixing description of some parameter.
> +
> + Fixes: abcdefgh1234 ("doc: add some parameter")
> + Cc: stable at dpdk.org
> +
> + Signed-off-by: Alex Smith <alex.smith at example.com>
>
you may also give reference to
http://dpdk.org/doc/guides/contributing/stable.html
> Creating Patches
> ----------------
>
More information about the dev
mailing list