From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Traynor Subject: [PATCH] doc: note validation commitment required for stables Date: Fri, 22 Mar 2019 11:44:00 +0000 Message-ID: <20190322114400.3745-1-ktraynor@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: stable@dpdk.org, bluca@debian.org, yskoh@mellanox.com, ferruh.yigit@intel.com, thomas@monjalon.net, stephen@networkplumber.org, Kevin Traynor To: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com Return-path: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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