From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by dpdk.org (Postfix) with ESMTP id 66E49326D; Wed, 27 Mar 2019 18:25:49 +0100 (CET) Received: by mail-wr1-f65.google.com with SMTP id p10so19598333wrq.1; Wed, 27 Mar 2019 10:25:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=u8UV2PM6BiZ5VDgM7+laUdl91OILkoRBvlodH6/VPZY=; b=VyI5VB98Ypwmtc9NxhUqw9OXW5zCQKALxiV/2xvVL0wI4RxKYREc3ZZlTtzesue2oW Fg3hBfIgy2eNTAfJrhf+qsVQPhcXsA3FpLrw1HAG3pAmRa8towH5Q9WL6R+MtlwfvEtT NHeCgXuOPdvyrdFp4oxZrdCqwEZHHvNRCy6yFyl9phA70vNfE0KbT5WHNYTfTufDRYU2 ooYRbMhvMjB/EbRK6kb6MWg/irpP1eLaeCgUyXeZRPgs+EsazBZ2lF6UVwUi2NCDBLUp Xv0jw4WTus/w2eiQxpYGG5x6tldLLNJHwwiZWZ7qOZKGpVDNunpmxBCvEUO90maUEcnt QUMw== X-Gm-Message-State: APjAAAWT6DhTgf9j11wzdT3Gj51Ine+JoZuake/FsP/DntjAxAejNpSU FS1mMowBkndi9FCsOQT3aMs= X-Google-Smtp-Source: APXvYqxOT7Scy9l029BlEYHWryIKapNsau7ZHFnI+GMfE+YlptdoqwsHgQn311e7GzJYYBseSYGX+w== X-Received: by 2002:a5d:428c:: with SMTP id k12mr24969008wrq.279.1553707548937; Wed, 27 Mar 2019 10:25:48 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:b00c:66c8:99df:336]) by smtp.gmail.com with ESMTPSA id y63sm316339wmb.31.2019.03.27.10.25.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Mar 2019 10:25:47 -0700 (PDT) Message-ID: <65000618657f3eef2b1ba5f802ea59bc0ff81d5e.camel@debian.org> From: Luca Boccassi To: Kevin Traynor , john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org Cc: stable@dpdk.org Date: Wed, 27 Mar 2019 17:25:47 +0000 In-Reply-To: <20190327172206.16187-1-ktraynor@redhat.com> References: <20190322114400.3745-1-ktraynor@redhat.com> <20190327172206.16187-1-ktraynor@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Mar 2019 17:25:49 -0000 On Wed, 2019-03-27 at 17:22 +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 > Also, as decided in the March 27th techboard, to facilitate user > planning, a release should be designated as a stable release > no later than 1 month after it's initial master release. >=20 > Signed-off-by: Kevin Traynor < > ktraynor@redhat.com > > > --- >=20 > v2: add 1 month deadline to designate as stable release. > I didn't add v1 acks, as this is something new. >=20 > doc/guides/contributing/stable.rst | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) >=20 > diff --git a/doc/guides/contributing/stable.rst > b/doc/guides/contributing/stable.rst > index 4214103b3..b63cd4228 100644 > --- a/doc/guides/contributing/stable.rst > +++ b/doc/guides/contributing/stable.rst > @@ -27,5 +27,7 @@ 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. If a release is to be > designated > +as a Stable Release, it should be done by 1 month after the master > release. > =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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 92365A05D3 for ; Wed, 27 Mar 2019 18:25:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AA7DB4F93; Wed, 27 Mar 2019 18:25:50 +0100 (CET) Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by dpdk.org (Postfix) with ESMTP id 66E49326D; Wed, 27 Mar 2019 18:25:49 +0100 (CET) Received: by mail-wr1-f65.google.com with SMTP id p10so19598333wrq.1; Wed, 27 Mar 2019 10:25:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=u8UV2PM6BiZ5VDgM7+laUdl91OILkoRBvlodH6/VPZY=; b=VyI5VB98Ypwmtc9NxhUqw9OXW5zCQKALxiV/2xvVL0wI4RxKYREc3ZZlTtzesue2oW Fg3hBfIgy2eNTAfJrhf+qsVQPhcXsA3FpLrw1HAG3pAmRa8towH5Q9WL6R+MtlwfvEtT NHeCgXuOPdvyrdFp4oxZrdCqwEZHHvNRCy6yFyl9phA70vNfE0KbT5WHNYTfTufDRYU2 ooYRbMhvMjB/EbRK6kb6MWg/irpP1eLaeCgUyXeZRPgs+EsazBZ2lF6UVwUi2NCDBLUp Xv0jw4WTus/w2eiQxpYGG5x6tldLLNJHwwiZWZ7qOZKGpVDNunpmxBCvEUO90maUEcnt QUMw== X-Gm-Message-State: APjAAAWT6DhTgf9j11wzdT3Gj51Ine+JoZuake/FsP/DntjAxAejNpSU FS1mMowBkndi9FCsOQT3aMs= X-Google-Smtp-Source: APXvYqxOT7Scy9l029BlEYHWryIKapNsau7ZHFnI+GMfE+YlptdoqwsHgQn311e7GzJYYBseSYGX+w== X-Received: by 2002:a5d:428c:: with SMTP id k12mr24969008wrq.279.1553707548937; Wed, 27 Mar 2019 10:25:48 -0700 (PDT) Received: from localhost ([2a01:4b00:f419:6f00:b00c:66c8:99df:336]) by smtp.gmail.com with ESMTPSA id y63sm316339wmb.31.2019.03.27.10.25.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Mar 2019 10:25:47 -0700 (PDT) Message-ID: <65000618657f3eef2b1ba5f802ea59bc0ff81d5e.camel@debian.org> From: Luca Boccassi To: Kevin Traynor , john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org Cc: stable@dpdk.org Date: Wed, 27 Mar 2019 17:25:47 +0000 In-Reply-To: <20190327172206.16187-1-ktraynor@redhat.com> References: <20190322114400.3745-1-ktraynor@redhat.com> <20190327172206.16187-1-ktraynor@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1 MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190327172547.d-5GxysYaDqZf18vm0RHdoxmlJ91Af89gvCZFj75LrY@z> On Wed, 2019-03-27 at 17:22 +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 > Also, as decided in the March 27th techboard, to facilitate user > planning, a release should be designated as a stable release > no later than 1 month after it's initial master release. >=20 > Signed-off-by: Kevin Traynor < > ktraynor@redhat.com > > > --- >=20 > v2: add 1 month deadline to designate as stable release. > I didn't add v1 acks, as this is something new. >=20 > doc/guides/contributing/stable.rst | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) >=20 > diff --git a/doc/guides/contributing/stable.rst > b/doc/guides/contributing/stable.rst > index 4214103b3..b63cd4228 100644 > --- a/doc/guides/contributing/stable.rst > +++ b/doc/guides/contributing/stable.rst > @@ -27,5 +27,7 @@ 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. If a release is to be > designated > +as a Stable Release, it should be done by 1 month after the master > release. > =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