From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 645812C60 for ; Thu, 2 Mar 2017 10:40:23 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2017 01:40:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,230,1484035200"; d="scan'208";a="231398530" Received: from yliu-dev.sh.intel.com ([10.239.67.162]) by fmsmga004.fm.intel.com with ESMTP; 02 Mar 2017 01:40:20 -0800 From: Yuanhan Liu To: web@dpdk.org Cc: Thomas Monjalon , Yuanhan Liu , John McNamara , Yu Liu Date: Thu, 2 Mar 2017 17:39:00 +0800 Message-Id: <1488447540-1154-1-git-send-email-yuanhan.liu@linux.intel.com> X-Mailer: git-send-email 1.9.0 Subject: [dpdk-web] [PATCH v2] add stable and LTS release plan X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 09:40:23 -0000 Cc: John McNamara Cc: Yu Liu Signed-off-by: Yuanhan Liu --- v2: - some great rewords from John - link to the stable contribute guide Note that I am not quite sure how the specific release date to be added in the Scheduling section. Something like following?

17.05

  • Proposal deadline: February 26
  • Integration deadline: March 30
  • Release: May 2
  • v17.02.1 Release: May 17
  • v16.11.2 Release: May 17
--- dev/roadmap.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/dev/roadmap.html b/dev/roadmap.html index dfd5e41..b0fca0f 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -91,6 +91,14 @@ integration deadline. Otherwise, they will be postponed to the next releases.

At the end of the merge window, the first release candidate is out.

The last period is 1 month long and is dedicated to bug fixing. +

Stable and LTS release

+

A new release will be made about every 3 months, shortly (around 3 + weeks) after an upstream release has been made. For example, v16.11.1 was + released shortly after v17.02. +

In general, there will be only one such release for a stable release. + For an LTS release, which has a longer maintenance period (2 years), + there will be several releases (.2, .3, etc). +

For more information, please check this guidance.

Scheduling

16.11

    -- 1.9.0