From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ktraynor@redhat.com> Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 122C14F93; Wed, 27 Mar 2019 18:22:11 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6B496C05CDFA; Wed, 27 Mar 2019 17:22:10 +0000 (UTC) Received: from rh.redhat.com (unknown [10.33.36.142]) by smtp.corp.redhat.com (Postfix) with ESMTP id B87BC5C23E; Wed, 27 Mar 2019 17:22:08 +0000 (UTC) From: Kevin Traynor <ktraynor@redhat.com> To: john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org Cc: bluca@debian.org, stable@dpdk.org, Kevin Traynor <ktraynor@redhat.com> Date: Wed, 27 Mar 2019 17:22:06 +0000 Message-Id: <20190327172206.16187-1-ktraynor@redhat.com> In-Reply-To: <20190322114400.3745-1-ktraynor@redhat.com> References: <20190322114400.3745-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 27 Mar 2019 17:22:10 +0000 (UTC) Subject: [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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 27 Mar 2019 17:22:11 -0000 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. 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. Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- v2: add 1 month deadline to designate as stable release. I didn't add v1 acks, as this is something new. doc/guides/contributing/stable.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 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. A Stable Release is used to backport fixes from an ``N`` release back to an -- 2.20.1 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 5BF24A05D3 for <public@inbox.dpdk.org>; Wed, 27 Mar 2019 18:22:12 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 370394F9B; Wed, 27 Mar 2019 18:22:12 +0100 (CET) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 122C14F93; Wed, 27 Mar 2019 18:22:11 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6B496C05CDFA; Wed, 27 Mar 2019 17:22:10 +0000 (UTC) Received: from rh.redhat.com (unknown [10.33.36.142]) by smtp.corp.redhat.com (Postfix) with ESMTP id B87BC5C23E; Wed, 27 Mar 2019 17:22:08 +0000 (UTC) From: Kevin Traynor <ktraynor@redhat.com> To: john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org Cc: bluca@debian.org, stable@dpdk.org, Kevin Traynor <ktraynor@redhat.com> Date: Wed, 27 Mar 2019 17:22:06 +0000 Message-Id: <20190327172206.16187-1-ktraynor@redhat.com> In-Reply-To: <20190322114400.3745-1-ktraynor@redhat.com> References: <20190322114400.3745-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 27 Mar 2019 17:22:10 +0000 (UTC) Subject: [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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Content-Type: text/plain; charset="UTF-8" Message-ID: <20190327172206.ntejaksD0xx1z5wj1vEdsN0-vUmNEIZaoWv8aVCSmAw@z> 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. 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. Signed-off-by: Kevin Traynor <ktraynor@redhat.com> --- v2: add 1 month deadline to designate as stable release. I didn't add v1 acks, as this is something new. doc/guides/contributing/stable.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 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. A Stable Release is used to backport fixes from an ``N`` release back to an -- 2.20.1