From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 590FA1B89E; Wed, 11 Apr 2018 01:28:21 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D611520B6A; Tue, 10 Apr 2018 19:28:20 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 10 Apr 2018 19:28:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:date:from:in-reply-to:message-id:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=mesmtp; bh=kOtfK/Gwn1fTGv 6G1WjD85TqVkIwMPPbOKPGLdQGtkE=; b=ltcH7M05VlEM7ZDG3KLYP3+IlVrXCq bKqdWV52eGqivNOeO4S7ZncLUq8N8ouQPQEx46W19XI2liQdktsx/DIfGfNoHS8P ak681tGMi6cMjIg/2g+U7tjxktMKr5S0LsQsmnPxTYSFtwdQANmsyliny+PfuoCC NxMfiLLUilcWc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:date:from:in-reply-to:message-id :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=kOtfK/Gwn1fTGv6G1WjD85TqVkIwMPPbOKPGLdQGtkE=; b=GoYqBveB eugCFfCEln4AQLkma/lEKKJOohlbgelqs5tOorAkHCHI4PiqAeaXqEgwhyjPfAq5 N6TWtvMdSWVnt/+NTanA9VvBPpcHXDYdR+uuBYj5MU9qbglqLZytF68jDqnLrhUl JoYW5FFnneb1Upl0+p59fSuvMmUQRyoRtbVtveDsSkx9Q5Vv5EbMNpK0I+0buwTR mTe+68Xup7HtffIQ8/5WIWNPwApHKdKHxndLyGQqYceVmmN6GI4Ed73SE6rrROEa 7NY+bh90tpLNLywfVNF2AtvedR0CQUgcXpI0LS9XJQUvXB/CFJd1Bo6wvRfbRO12 gaSCVZazQIAWRw== X-ME-Sender: <xms:lEjNWnn0C16bkqBTcuTYf9WoNlr2UaVlaq7F3GK5KN5tGkTsYpIy5g> Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B6515E4394; Tue, 10 Apr 2018 19:28:19 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: web@dpdk.org Cc: dev@dpdk.org, techboard@dpdk.org, bluca@debian.org, yliu@fridaylinux.org, ktraynor@redhat.com, christian.ehrhardt@canonical.com, yskoh@mellanox.com Date: Wed, 11 Apr 2018 01:28:13 +0200 Message-Id: <20180410232813.2534-1-thomas@monjalon.net> X-Mailer: git-send-email 2.16.2 In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net> References: <20180309133612.19927-1-thomas@monjalon.net> Subject: [dpdk-dev] [PATCH v2] update stable releases roadmap 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://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 10 Apr 2018 23:28:21 -0000 Signed-off-by: Thomas Monjalon <thomas@monjalon.net> --- Patch for the website (to web@dpdk.org) Cc'ed to dev@dpdk.org v2: - more volunteers - propose to do .1 release after -rc1 of next branch. --- dev/roadmap.html | 37 ++++++++++++++++++++++++++++++++----- 1 file changed, 32 insertions(+), 5 deletions(-) diff --git a/dev/roadmap.html b/dev/roadmap.html index e6cf640..c7cd7cb 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -97,13 +97,15 @@ <li>Integration deadline: June 29, 2018 <li>Release: August 1, 2018 </ul> - <p>18.11 + <p>18.11 (LTS) <ul> <li>Proposal deadline: September 7, 2018 <li>Integration deadline: October 5, 2018 <li>Release: November 2, 2018 </ul> <h2 id="stable">Stable releases</h2> + <p>There is a documentation page describing the + <a href="/doc/guides/contributing/stable.html">guidelines of the stable releases</a>. <p>Stable point releases follow mainline releases. <p>After each -rc tag and after the final version, relevant bug fixes get backported by the stable maintainers into the respective branches in "bursts". @@ -111,8 +113,9 @@ to stable@dpdk.org only (avoiding dev@dpdk.org). <p>After all the relevant bugfixes have been backported, regression tests are ran, and if clear, the stable release is announced. - <p>Typically a new stable release version follows a mainline release - by 1-2 weeks, depending on the test results. + <p>The first stable release (.1) of a branch should follow + its mainline release (.0) by at least two months, + after the first release candidate (-rc1) of the next branch. <hr> <div style="overflow-x:auto"> <table> @@ -125,15 +128,39 @@ <tr> <td>16.11.6</td> <td>May 19, 2018</td> - <td>November 2018</td> + <td>November 2018 (LTS)</td> <td>Luca Boccassi</td> </tr> <tr> <td>17.11.2</td> <td>May 19, 2018</td> - <td>November 2019</td> + <td>November 2019 (LTS)</td> <td>Yuanhan Liu</td> </tr> + <tr> + <td>18.02.1</td> + <td>April 6, 2018</td> + <td>June 2018</td> + <td>Luca Boccassi</td> + </tr> + <tr> + <td>18.05.1</td> + <td>June 29, 2018</td> + <td>October 2018</td> + <td>Christian Ehrhardt</td> + </tr> + <tr> + <td>18.08.1</td> + <td>October 5, 2018</td> + <td>January 2019</td> + <td>looking for volunteer</td> + </tr> + <tr> + <td>18.11.1</td> + <td>January 11, 2019</td> + <td>November 2020 (LTS)</td> + <td>Kevin Traynor</td> + </tr> </table> </div> </section> -- 2.16.2