From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E818D1B81D for ; Thu, 8 Feb 2018 21:42:49 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7128121053; Thu, 8 Feb 2018 15:42:49 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 08 Feb 2018 15:42:49 -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=3qsJMdGEfhL0l3H05+dlPvkhxS x9HvI/cehmYqTnyqs=; b=svrwI7rJeAceQljX7ftjwNG+RbY2cSxQ1UVsp3Izgo mvI5WciOH8diYAb6xLa3/SdjVyk1NJq9tf/bpQSCl7cNN825LThWQ+sqya4dtXl2 LA+6PaSbyIcKvdVjAPhKUgYEP1RQQegqlYH5X/+0QoLqzK77jUDm3F7h+vqd7ZDT E= 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=fm1; bh=3qsJMd GEfhL0l3H05+dlPvkhxSx9HvI/cehmYqTnyqs=; b=Kzn710Xc8Gn3JaXYPVPX/h W1Zct+JMfKm4T8u71xuxdprGwFAiRaJ8+bQl98QifjS7zetn0X5AV69wLYG/qL98 1dhWrtiCzCxa9hWks/xkZa9AvEiHh4HFOjCTh23bHv031jfaxsr67eENsTLzKHY6 R3ANJiIprFVs2sLC22vRV9jj9N+O2sns+K/0Ib7ELrMcYLrW8faliVRb0PDJaVO0 ljYd/7Nb71dcQX9CGZJleNoBqiJQWbfPOZlBcS458BxPysj64pbwkSxDn/1QUP10 +G/KJtgBzipFAxJQHdRrIzfHoxhIzQXnoNzgIGDUiduFqF/Aiba3GNwr6s4Rmtlw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 22201240DE; Thu, 8 Feb 2018 15:42:49 -0500 (EST) From: Thomas Monjalon To: Luca Boccassi Cc: web@dpdk.org, yliu@fridaylinux.org Date: Thu, 08 Feb 2018 21:42:44 +0100 Message-ID: <1610947.Pusgb9ZLHA@xps> In-Reply-To: <1518114299.15424.76.camel@debian.org> References: <20180208182142.6189-1-bluca@debian.org> <1518114299.15424.76.camel@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [RFC] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2018 20:42:50 -0000 08/02/2018 19:24, Luca Boccassi: > On Thu, 2018-02-08 at 18:21 +0000, Luca Boccassi wrote: > > Signed-off-by: Luca Boccassi > > --- > > dev/roadmap.html | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/dev/roadmap.html b/dev/roadmap.html > > index a2fea2f..c818bde 100644 > > --- a/dev/roadmap.html > > +++ b/dev/roadmap.html > > @@ -111,5 +111,15 @@ > >
  • Integration deadline: September 28, 2018 > >
  • Release: November 2, 2018 > > > > +

    LTS releases

    > > +

    LTS point releases follow mainline releases. > > +

    After each -rc tag and after the final version, relevant > > bug fixes get > > + backported by the LTS maintainers into the respective > > branches. > > +

    Developers can provide LTS-specific patches by sending > > them to stable@dpdk.org > > + only. > > +

    After all the relevant bugfixes have been backported, > > regression tests are ran, > > + and if clear, the LTS is announced. > > +

    Typically a new LTS version follows a mainline release by > > 1-2 weeks, depending > > + on the test results. > > > >

    > > Thomas, > > Is this what you had in mind? Let me know if there are any changes > you'd like. You should talk about stable releases, LTS being some of them. In current process, patches are applied in burst after -rc, right? I think this burst mode is important to highlight. Please, could you add a roadmap for each branch? The roadmap could show EOL dates and the LTS ones. > And also please test how it looks before applying :-) You can test with "make". On my machine I use "make PYTHON2=python2".