[dpdk-dev] [PATCH] doc: note validation commitment required for stables

Kovacevic, Marko marko.kovacevic at intel.com
Mon Mar 25 11:14:20 CET 2019


> Subject: [PATCH] doc: note validation commitment required for stables
> 
> If a stable branch for a specific DPDK release is to proceed, along with
> needing a maintainer, there should also be commitment from major
> contributors for validation of the releases.
> 
> Signed-off-by: Kevin Traynor <ktraynor at redhat.com>
> ---
>  doc/guides/contributing/stable.rst | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..0130991e2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,6 @@ Stable Releases
> 
>  Any major release of DPDK can be designated as a Stable Release if a -
> maintainer volunteers to maintain it.
> +maintainer volunteers to maintain it and there is a commitment from
> +major contributors to validate it before releases.
> 
>  A Stable Release is used to backport fixes from an ``N`` release back to an
> --

Acked-by: Marko Kovacevic <marko.kovacevic at intel.com>


More information about the dev mailing list