From: Kevin Traynor <ktraynor@redhat.com>
To: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Cc: stable@dpdk.org, bluca@debian.org, yskoh@mellanox.com,
ferruh.yigit@intel.com, thomas@monjalon.net,
stephen@networkplumber.org, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH] doc: note validation commitment required for stables
Date: Fri, 22 Mar 2019 11:44:00 +0000 [thread overview]
Message-ID: <20190322114400.3745-1-ktraynor@redhat.com> (raw)
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
--
2.20.1
next reply other threads:[~2019-03-22 11:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 11:44 Kevin Traynor [this message]
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
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=20190322114400.3745-1-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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).