From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Traynor Subject: [PATCH v2] doc: note validation and timeline required for stables Date: Wed, 27 Mar 2019 17:22:06 +0000 Message-ID: <20190327172206.16187-1-ktraynor@redhat.com> References: <20190322114400.3745-1-ktraynor@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: bluca@debian.org, stable@dpdk.org, Kevin Traynor To: john.mcnamara@intel.com, marko.kovacevic@intel.com, dev@dpdk.org 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" 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 --- 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