From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 19C7710B7 for <web@dpdk.org>; Tue, 6 Mar 2018 12:25:47 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 887B020C59; Tue, 6 Mar 2018 06:25:45 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 06 Mar 2018 06:25:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ujVBJpv5H2pJAWcLcQyu0AVrcb AqhL5SOs+v9nvYGco=; b=R8Rdirnx1rUlTKtPiBitA/wgKtisk0Ysv/egB5Pp+M cuKiLl6QxjqS0VZHZp4XtP3FbSZBxtmDouelHgMIb4Xg+CXDQYvC+rkezDYx9yoz KTFVIXe11gMoaasZ2ItJ4zg6oqXmDtA0SlJiHzyUfCorvoS2hExMle6xxpG95Cd2 0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ujVBJp v5H2pJAWcLcQyu0AVrcbAqhL5SOs+v9nvYGco=; b=j+z9XUNmOUvKlCxVPMgwdN lQJ9eXtkKq/Nb568uYuGERU+MyvTmSZF4J3KYBjwEkOK/vFRfd6g9JDuIHmCWK5p TvDx2KEJU80br9a52H+NOJje36xHSfvpp/mQQ0ams9AZ3MZAe/NRYOVE7MFs4HLk GAe4ZeZxDGk0NhhWRCaaQNxNjN/UYrwwTMd1LmOg0QDdnz926JUUv/ArQtZqRRE/ NG7xY6WrehTQALHHKprXdIw+5ZWNHctzBybPMikDtfjD6w4fbJiSfhW+hCdf8w4c KTNF2tInQixtGHB3Jb/TKyzFJAvQ2gnEQdcEmO3bgyGp9hmfe4VEETmu78UUl1hQ == X-ME-Sender: <xms:uXqeWuomoTdpDX36BKc5LcKMnXnoychLpMeXMPoLyuEGsKoyQoG-ug> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id D57BF24608; Tue, 6 Mar 2018 06:25:44 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Luca Boccassi <bluca@debian.org>, yliu@fridaylinux.org Cc: web@dpdk.org Date: Tue, 06 Mar 2018 12:25:44 +0100 Message-ID: <3266586.a8klAloIbi@xps> In-Reply-To: <20180209130440.20380-1-bluca@debian.org> References: <20180208182142.6189-1-bluca@debian.org> <20180209130440.20380-1-bluca@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [RFC v2] Add LTS section on the roadmap page X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance <web.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/web>, <mailto:web-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/web/> List-Post: <mailto:web@dpdk.org> List-Help: <mailto:web-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/web>, <mailto:web-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 06 Mar 2018 11:25:47 -0000 Hi Luca, Sorry I forgot this patch you sent one month ago. 09/02/2018 14:04, Luca Boccassi: > + <h2 id="stable">Stable releases</h2> > + <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". > + <p>Developers can provide stable-specific patches by sending them 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. It is a good description of the current process. When this patch is applied, I would like to discuss having a first stable release before the next major release. > + <h3 id="stable">Stable releases roadmap</h3> No need for this title if below is a table. > + <p>16.11 is an LTS release, and is going to be maintained by Luca Boccassi until the end of > + 2018, with the latest point release following the release of 18.11 in November 2018. > + <p>17.11 is an LTS release, and is going to be maintained by Yuanhan Liu until the end of > + 2019, with the latest point release following the release of 19.11 in November 2019. We should include non LTS releases and make it a table: branch next version date end of life maintainer