From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Boccassi Subject: Re: [PATCH] doc: note validation commitment required for stables Date: Fri, 22 Mar 2019 13:30:06 +0000 Message-ID: <072efbd3bb3812b01a0da69c8fc0a6e67828c9bd.camel@debian.org> References: <20190322114400.3745-1-ktraynor@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: stable@dpdk.org, yskoh@mellanox.com, ferruh.yigit@intel.com, thomas@monjalon.net, stephen@networkplumber.org To: Kevin Traynor , dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com Return-path: In-Reply-To: <20190322114400.3745-1-ktraynor@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. >=20 > Signed-off-by: Kevin Traynor > --- > doc/guides/contributing/stable.rst | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) >=20 > 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 > =20 > 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. > =20 > A Stable Release is used to backport fixes from an ``N`` release > back to an Acked-by: Luca Boccassi --=20 Kind regards, Luca Boccassi