diff mbox series

doc: note validation commitment required for stables

Message ID 20190322114400.3745-1-ktraynor@redhat.com (mailing list archive)
State Superseded, archived
Delegated to: Thomas Monjalon
Headers
Series doc: note validation commitment required for stables |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/Intel-compilation success Compilation OK

Commit Message

Kevin Traynor March 22, 2019, 11:44 a.m. UTC 
  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@redhat.com>
---
 doc/guides/contributing/stable.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Comments

Luca Boccassi March 22, 2019, 1:30 p.m. UTC | #1 
On Fri, 2019-03-22 at 11:44 +0000, Kevin Traynor wrote:
> 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@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: Luca Boccassi <bluca@debian.org>
Kovacevic, Marko March 25, 2019, 10:14 a.m. UTC | #2 
> 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@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@intel.com>
diff mbox series

Patch

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