From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f180.google.com (mail-wr0-f180.google.com [209.85.128.180]) by dpdk.org (Postfix) with ESMTP id 98D3D14EC for ; Wed, 8 Feb 2017 15:39:24 +0100 (CET) Received: by mail-wr0-f180.google.com with SMTP id 89so61722696wrr.2 for ; Wed, 08 Feb 2017 06:39:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=fCAL/m7AjRw/hYArdDASOIbgnvvUsGimoxtQ8mmCSVY=; b=HJlDEniAsUhG504uEyR8sK3+MklmOI/6/f6K471wMl9mvEMtBkI3lcTHNCwjUKCqL6 tJFh1Ig6J11cyj2KaVewWmVGctutEBljqZng9QkePezdXT17wt4pnR+yOtzS/nn9CSyW jfHSu0CXTq/pOqyN/+TiiRg0ajBGwgQaZErYkUgqrxftk0ixfNamD5q2ygqb1i4NvTHk V8d6hIjVv5vveWKkfNQzlCMWoIEKyJjM1nYSlv4q+icXXuiz5Z38oMrBxGZ1rDTfwRUj 1vWvrgSsLwB4P9SmCbeemtN4IX02fVlQ/0uVrBcPjVfsW6+uNmgMh1PPjjwYfrDtRzEO f4iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=fCAL/m7AjRw/hYArdDASOIbgnvvUsGimoxtQ8mmCSVY=; b=B4OJIG9y6iV42xYcI48PjYE9WzqQsuLWlpND5Gi5IZv1nolPqHQKMo8Lg86/uPn9Rx LjgN5mwLzZl3jCrAx9Jtp0Vh5rSsWE+DIkrERJQfo2+zteHNzN9xQqPj/CGC3Yhl7yK8 JUm4966ai4eOVUWBBhXLv65zuduXtPAYbRyW63kjgZWKdN5DOFeFh0XTr55HgfTNHkPR 2zZ/xgVdKhMFnMfd76CndHGVwqw4THy5v8oN9cjcfmaZeeL6V9fq7fM6f92MZYLhYNIt AqUfTnSpsZgoM6OXf/4ZdA2ofzmcWvgUjFdoqUDSxFi3RRiIBVFltkkadHzJwK1fz55Y ki9w== X-Gm-Message-State: AIkVDXL5/RIpNSseQT+fVjFaFrAzdU9iVbSRua6mWhR6glM6b281WdAbvSqw23WDeZKz4reT X-Received: by 10.223.173.40 with SMTP id p37mr21365823wrc.136.1486564764353; Wed, 08 Feb 2017 06:39:24 -0800 (PST) Received: from xps13.localnet (177.21.90.92.rev.sfr.net. [92.90.21.177]) by smtp.gmail.com with ESMTPSA id u42sm13353605wrc.1.2017.02.08.06.39.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 06:39:23 -0800 (PST) Date: Wed, 08 Feb 2017 06:39:23 -0800 (PST) X-Google-Original-Date: Wed, 08 Feb 2017 15:39 +0100 From: Thomas Monjalon To: Yuanhan Liu Cc: John McNamara , dev@dpdk.org, stable@dpdk.org Message-ID: <1841036.sU38etbx4S@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20170120084330.GY9046@yliu-dev.sh.intel.com> References: <20170120084330.GY9046@yliu-dev.sh.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [PATCH v1] doc: add guidelines on stable and lts releases X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 14:39:24 -0000 2017-01-20 16:43, Yuanhan Liu: > 16.07 as a first trial of stable release, I made a proposal to have 2 > releases: v16.07.1 shortly after v16.11-rc1 and v16.07.2 shortly after > v16.11. While the gap between v16.07 and v16.11 are 4 months, doing a > release each 2 month doesn't seem that bad. It may a bit stretch then > because the gap is shorter (3 months) since 16.11. Besides, the validation > team here are pretty busy after rc1, meaning it doesn't seem a good idea > to have another release shortly after that: they may quite be burdened. > > So I'm proposing to make one stable/LTS release per release cycle. For > example, we will have v16.11.1 shortly after v17.02, and judging that > v16.11 is a LTS release, we will have v16.11.2 after v17.05, and so on. > > And my plan towards a release is, I will monitor (by a script) the > official tree regularly (normally, weekly), and pick patches from there > if any to a specific stable branch. As before, an email notification will > be sent to the author and all email addresses mentioned in the patch > (normally, they are maintainers, reviewers, etc) once a patch is picked > as a stable candidate. > > Doing this regularly, hopefully, tells people that DPDK stable/LTS is > live and actively maintained. > > Any objections? If no, I could start picking patches since the beginning > of next week. OK, thanks Yuanhan. Have you received any proposal to help or maintain a future stable branch?