DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"bluca@debian.org" <bluca@debian.org>,
	"yskoh@mellanox.com" <yskoh@mellanox.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
Date: Mon, 25 Mar 2019 10:14:20 +0000	[thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F66020AC297@IRSMSX104.ger.corp.intel.com> (raw)
Message-ID: <20190325101420.1NqAfM6AuziyJgjdYBhTD2P2sn0cfVAXy2T0xhisIuM@z> (raw)
In-Reply-To: <20190322114400.3745-1-ktraynor@redhat.com>

> 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>

  parent reply	other threads:[~2019-03-25 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 11:44 Kevin Traynor
2019-03-22 11:44 ` Kevin Traynor
2019-03-22 13:30 ` Luca Boccassi
2019-03-22 13:30   ` Luca Boccassi
2019-03-25 10:14 ` Kovacevic, Marko [this message]
2019-03-25 10:14   ` Kovacevic, Marko
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
2019-03-27 17:22   ` Kevin Traynor
2019-03-27 17:25   ` Luca Boccassi
2019-03-27 17:25     ` Luca Boccassi
2019-04-05 13:36     ` Thomas Monjalon
2019-04-05 13:36       ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6DC05C7C5F25994B81B3F2F214251F66020AC297@IRSMSX104.ger.corp.intel.com \
    --to=marko.kovacevic@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=yskoh@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).